I hope this becomes a standard part of the “no easter eggs in cURL?!” discourse that makes such frequent appearances on this site. If we must keep discussing it.
One product I worked on (ahem, no names) we had written an easter egg and hooked it up and everything, then we got cold feet. Not because of any silly rules, but because we realized it truly would have been bad for the product and the company if the egg had caused something to go haywire. We looked at each other, then unanimously decided to remove it. Masking the true purpose of that check-in was actually much harder than hiding the egg to begin with. :-)
"I'm a pro-easter egg ideologue and will tolerate no software that does not contain such silliness, nor should any other rational, stable, intelligent person!"
There, now it's your turn.
But unless I know your position on Easter eggs then I cannot accurately determine to hate you or not.
Q.E.D.
But having them in heavily used security critical programs like curl is just asking for a heartbleed/log4j/etc type incident.