|
|
|
|
|
by tpmoney
253 days ago
|
|
The lack of Easter eggs in programs I feel like is a combination of 3 things 1) more “professionalism” being expected in software. Computers aren’t quirky things anymore they’re “serious business” and “serious businesses don’t do quirky”. Or some other such nonsense. 2) Offense risk, something innocuous has serious potential to be taken wrong now or even at some future date. I worked on a system where we needed to impose some effectively arbitrary max limit on the number of items allowed to be configured. We eventually settled on “640k” and originally had an error if you exceed that that said “640k ought to be enough for anyone”. The devs who would have seen that message would have gotten the reference and hopefully had a good chuckle. But I’ve seen customers get short about innocuous jokes before and could easily have seen someone complaining that we weren’t taking their needs seriously. 3) Security liability. A lot of Easter eggs were distinct code paths or sometimes even entire tiny embedded applications. In an ever connected world where your credit card terminal might be the gateway to your entire customer database, any unnecessary code path is also a potential security hole and risk. No one really wants to be in the news because a cute joke their developers put in 4 years ago was the key to a massive exploit. Still I do agree that I miss some the “personality” older software could have. |
|