alt Hacker News> Microsoft had a "no easter eggs" policy starting in the early 2000s
Note that this was in the aftermath of a summer with multiple major XP security issues.
Replies
PhasmaFelis • 06/24/2025
Wasn't it also something to do with supplying government contracts, which require all behavior to be documented?
reconnecting • 06/24/2025
Microsoft best ever easter eggs was C:\CON\CON
baq • 06/24/2025
came here to say that, too.
imagine your easter egg introduced a vulnerability. a blanket policy like that is literally the first document leadership signs and sends out.
Were there any Microsoft XP security issues caused by "Easter eggs" prior to that policy change? Or was this just put in place as a policy because it was easy to put in place?