Live data from Hacker News

Mister Macintosh (2004)

folklore.org

51–59 of 59 posts

Re: Mister Macintosh (2004)

#51
post #8

Sort of like a reverse Clippy, which you do find easily and wish you wouldn't. Generally speaking, programs used to have more Easter eggs. I can't recall a single one in the cloud era. The only one remotely whimsical is PostHog.

I'd much rather have Clippy than the forced AI shit that's everywhere nowadays

Re: Mister Macintosh (2004)

#52
post #48
post #37

Earlier quoted context omitted.

Given that (I think?) the "OK/Cancel" dialog of the original Mac is one of those 'foundational' UI conventions that was copied pretty directly by every GUI that came after it, I am very curious if our world wouldn't be full of "Do It" buttons if this episode hadn't taken place. Even the Start Menu could have been called the "Do" menu in that alternate universe.

Interestingly, Apple's HIG generally suggest avoiding "Ok" in favor of an action describing what will happen. So save dialogs say "Save" not "OK". The empty trash dialog says "Empty Trash". Still I guess that's more clear than "Do It"

This change most likely happened sometime in the early 1990s, though it’s possible it could’ve happened in the late 1980s. I have a PDF copy of the Macintosh Human Interface Guidelines from 1995 that recommends descriptive button text instead of “OK” and “Cancel.”

Re: Mister Macintosh (2004)

#53
post #27
post #8

Sort of like a reverse Clippy, which you do find easily and wish you wouldn't. Generally speaking, programs used to have more Easter eggs. I can't recall a single one in the cloud era. The only one remotely whimsical is PostHog.

I feel that GNU Terry Pratchett is a cute little harmless easter egg that can be easily implemented: https://gnuterrypratchett.com/ https://www.theregister.com/ have it for instance.

I also like the extension of this to other figures important to a community. I founded a community called MiloHax that centers around modding and learning from the game made by Harmonix Music Systems, and we serve X-Clacks-Overhead with Sir Terry's name as well as some other influential people, both inside and outside of the community.

Re: Mister Macintosh (2004)

#54
post #43
post #8

Sort of like a reverse Clippy, which you do find easily and wish you wouldn't. Generally speaking, programs used to have more Easter eggs. I can't recall a single one in the cloud era. The only one remotely whimsical is PostHog.

I know MS put the kibosh on most easter eggs after some "trustworthy software" initiative in the early 2000s, which I think was to assuage government concerns that they could also be sneaking malicious backdoors into their software (silly reasoning), or that there could be vulnerabilities caused by an easter egg (ehhh...maybe).

It's not unreasonable to think that Easter eggs might be written to contain back doors. Certainly any large software project that has workflow gaps where unvetted code can be introduced is a recipe for disaster.

Re: Mister Macintosh (2004)

#55
post #54
post #43

Earlier quoted context omitted.

I know MS put the kibosh on most easter eggs after some "trustworthy software" initiative in the early 2000s, which I think was to assuage government concerns that they could also be sneaking malicious backdoors into their software (silly reasoning), or that there could be vulnerabilities caused by an easter egg (ehhh...maybe).

It's not unreasonable to think that Easter eggs might be written to contain back doors. Certainly any large software project that has workflow gaps where unvetted code can be introduced is a recipe for disaster.

Why make the backdoor obvious by incorporating an easter egg when you could just make one that does not draw attention to itself? You can still make non-obvious backdoors with this policy in place.

Re: Mister Macintosh (2004)

#56
post #55
post #54

Earlier quoted context omitted.

It's not unreasonable to think that Easter eggs might be written to contain back doors. Certainly any large software project that has workflow gaps where unvetted code can be introduced is a recipe for disaster.

Why make the backdoor obvious by incorporating an easter egg when you could just make one that does not draw attention to itself? You can still make non-obvious backdoors with this policy in place.

An Easter egg containing a funny animation can be used to distract from the malformed image that serves as a back door that exploits a bug in the image renderer.

Re: Mister Macintosh (2004)

#58
post #56
post #55

Earlier quoted context omitted.

Why make the backdoor obvious by incorporating an easter egg when you could just make one that does not draw attention to itself? You can still make non-obvious backdoors with this policy in place.

An Easter egg containing a funny animation can be used to distract from the malformed image that serves as a back door that exploits a bug in the image renderer.

This guy f̶hacks.

Re: Mister Macintosh (2004)

#59
post #21

The idea of getting Mr Macintosh instead of a menu occasionally would be UX nightmare. But there could be other cute places to include it, like occasionally it's present inside About My Mac or whatever.

This is a near perfect implementation as it doesn't actually affect the UX in anyway at all. Perhaps in more modern version he could appear behind a widget or something in the notification centre.
Post reply on HN