Reading this makes me wonder if Easter eggs are ever appropriate for something as ubiquitous as man.
Which means you need to usually make it explicit to call them (man --abba or something) than something that "surprises" the user.
They fell out of favor when people realized they were a security issue, because it was a code path that rarely got tested.
Proper code doesn't either, and yet there they are! The point is they added another attack surface, however small, and another code path that should be tested.
When people started to care about 100% test coverage, they started to disappear.
I dunno, "attack surface" to me means "facilitate opening/vulnerability somehow" and none of the easter egg code I've seen has done that. You have any concrete examples where a easter egg made possible a security vulnerability that wouldn't be possible otherwise?
But yes, another code path created by easter eggs that wasn't tested I've seen countless of times, but never been an issue, but maybe our easter eggs always been too small in scope for that.
https://security.stackexchange.com/questions/144202/are-ther...
In Star Trek: 25th Anniversary, we had a hidden animation of Captain Kirk's toupee jumping off his head and running out of the room. It was caught before release and they made us take it out since no one wanted to piss off William Shatner.