5/30/2026 at 8:16:42 PM
https://folklore.org/The_Father_of_The_Macintosh.html:“There's no doubt that Jef was the creator of the Macintosh project at Apple, and that his articulate vision of an exceptionally easy to use, low cost, high volume appliance computer got the ball rolling, and remained near the heart of the project long after Jef left the company. He also deserves ample credit for putting together the extraordinary initial team that created the computer, recruiting former student Bill Atkinson to Apple and then hiring amazing individuals like Burrell Smith, Bud Tribble, Joanna Hoffman and Brian Howard for the Macintosh team. But there is also no escaping the fact that the Macintosh that we know and love is very different than the computer that Jef wanted to build, so much so that he is much more like an eccentric great uncle than the Macintosh's father.
Jef did not want to incorporate what became the two most definitive aspects of Macintosh technology - the Motorola 68000 microprocessor and the mouse pointing device. Jef preferred the 6809, a cheaper but weaker processor which only had 16 bits of address space and would have been obsolete in just a year or two, since it couldn't address more than 64Kbytes. He was dead set against the mouse as well, preferring dedicated meta-keys to do the pointing. He became increasingly alienated from the team, eventually leaving entirely in the summer of 1981, when we were still just getting started, and the final product utilitized very few of the ideas in the Book of Macintosh. In fact, if the name of the project had changed after Steve took over in January 1981, and it almost did (see Bicycle), there wouldn't be much reason to correlate it with his ideas at all.”
by Someone
5/30/2026 at 8:53:19 PM
In TFA, Jef Raskin claims that the story about the mouse is not entirely correct:JR: No. I designed it to be graphical from the ground up. But the text portions of the interface, which I also cared about, would have been cleaner. People have put together my dislike of the mouse (confusing dislike for a particular input device with dislike for graphic input devices in general; I personally prefer trackballs and tablets) and my careful attention to text handling to a false legend of my wanting a text-based machine. Andy [Hertzfeld, a major developer on the early Mac team], unfortunately, has not generally gone back to the original documents, and he’s interviewed lots of people about the history of the Mac, but not me. His website is, as a result, full of errors.
by adrian_b
5/30/2026 at 11:00:36 PM
History is written by the victors. In this case it’s completely fine, as Raskin’s “corrections” don’t really amount to much, and certainly would have led to a path where Macintosh was just another abandoned experiment like the Apple III.Perhaps in this alternate universe, a substantially reworked “Lisa II” might have been Apple’s long-lived computing platform.
by simondotau
5/31/2026 at 12:36:38 AM
The corrections may not amount to much, but there is no reason to believe that his version would be a failed experiment like the Apple III or the Lisa would have taken it's place.Part of the magic of the Macintosh was the simplicity of the hardware. In that respect, it was much closer to the Apple II than the Apple III or Lisa. Consumers may not think much about what's inside the case, but it matters when it comes to manufacturing costs and that translates into the cost for consumers. While the original Macintosh was by no means cheap, it was about half the cost of the Apple III and a quarter of the cost of the Lisa. Heck, even the adoption of the Macintosh was slow because of its price. Maybe a less expensive 6809 based Macintosh would have had more success in the market, at least early on. It's also too easy to read too much into the failure of the Canon Cat. The Canon Cat was introduced years later. User expectations were starting to solidify around the GUI at that point. (Then again, success was not guaranteed. Lacking compatibility with the Apple II would have held it back. Especially so after the introduction of the IBM PC since the IBM PC had IBM backing it.)
I also think the adoption of the GUI for consumer computers would have been delayed considerably without the Macintosh 128k. Early machines that supported a GUI tended to be expensive. Early versions of Windows were crude. The only real outliers in that respect were the Atari and the Amiga. Would they have supported a GUI without Apple taking that first step? It's hard to tell.
by II2II
5/31/2026 at 6:38:26 PM
> While the original Macintosh was by no means cheap, it was about half the cost of the Apple IIIMade me look it up! I was developing Apple ][/III/Lisa/Mac software at the time. I used the Apple III to write Apple Pascal for the Apple ][, and the Lisa to develop for the Mac. I'd completely forgotten the initial pricing of the Apple III, which was stratospheric. The $7,800 config was 256K I think (~$31K in today's dollars).
"It sold initially for between $4,340 and $7,800, depending on the configuration. The original Apple III had many problems, and was replaced by a revised model in mid 1981, which featured 256K RAM, updated system software, and a lower price ($3495). A 5 MB external hard disk was also made available. The Apple /// sold very poorly and was replaced by the Apple ///+ ($2995) in Late 1983. The Apple ///+ was discontinued in 1985."
by getpost
5/31/2026 at 2:55:35 AM
The defining aspect of the Macintosh for me will always be the mandatory GUI - most everything else had it as either an entire afterthought, or at least as a “program started later”.by bombcar
5/31/2026 at 10:44:46 AM
The mandatory graphic GUI - and MacPaint - made the point that the Mac was primarily a visual design tool that happened to handle text.That was absolutely revolutionary.
S-100 systems and the early PCs were primarily text systems that sometimes happened to do crude graphics.
The original Apple II tried to do graphics but the tech to do it properly just didn't exist. And the underlying UI was still text based.
Raskin's Mac vision didn't make that leap. It wasn't just about the mouse, it was about the philosophy of the product. Raskin wanted text-but-cheaper-and-better, Jobs wanted pictures and art.
by TheOtherHobbes
5/31/2026 at 11:48:53 AM
> The mandatory graphic GUI...What do you reckon the "G" in GUI stands for, out of curiosity?
by michaelcampbell
5/31/2026 at 10:40:53 AM
And perhaps most critically, other semi-GUI platforms made lesser attempts to demand consistency.by simondotau
5/31/2026 at 11:40:37 AM
Early on, sure. I seem to recall Apple having their Human Interface Guidelines early on, which helped, yet there were developers who were either unaware of them or experimenting with different ideas. Other platforms tried to improve consistency later on though. For example: there was CUA for IBM. Of course, most of that went out the windows in the late 1990's and early 2000's when companies figured out that the easiest way to differentiate their products to consumers was visually, rather than technically.by II2II
5/31/2026 at 12:50:05 AM
Lisa 2 was cheaper than many later Macs, but the Mac folks seemed to have little interest in convergent evolution for the platforms or in integrating Lisa features like memory protection into the Mac. The result was that Lisa died as the Macintosh XL (ex-Lisa), with a Mac compatibility environment (MacWorks, which looked terrible with the stock Lisa rectangular pixels but better with a "Screen Kit" square pixel upgrade) as a consolation prize, while Mac users had to wait until Mac OS X for memory protection. Ultimately the Lisa hardware was able to run 68K versions of Mac OS through 7.6.1 in 1997.by musicale
5/31/2026 at 1:13:00 AM
Assuming the Mac folks had no interest in converging the platform in favour of the Lisa is somewhat unfair. While it sounds like some code was shared between the two platforms, the Lisa's operating system was quite different. It would have been difficult to make Lisa software operate under the Macintosh System Software. To my knowledge, there was virtually no software for the Lisa anyhow. Breaking software compatibility on the Macintosh to get the benefits of Lisa would have been a terrible business decision.Aside from that, the MMU in the Lisa would have been a custom solution which Apple would have to support. When Motorola introduced an MMU, it was for 68020 generation machines. Apple should have been able to introduce memory protection at that point, but didn't. One of the reasons was that Apple struggled to make that next generation operating system while retaining compatibility with existing software (albeit, memory protection may have been only one of many problems). This was by no means a problem exclusive to Apple. Other platforms ran into similar issues.
by II2II
5/31/2026 at 1:27:27 AM
Apple doesn't seem to have leveraged or combined work on (Lisa, Lisa Smalltalk, Lisa Xenix, Mac OS, A/UX, ...) as successfully as they might have. As you note, protected memory was deferred to multiple failed Mac OS successor projects (Pink/Taligent, Copland/NuKernel, etc.) Ultimately Apple gave up, acquired Steve Jobs and NeXT, and eventually successfully migrated the Mac platform to an OS with memory protection.Since then however Apple's OS and hardware strategy has been much more coherent, with macOS, iOS, iPadOS, tvOS, watchOS etc. sharing code, and sharing SoC technology as well. Ironically this is similar to Microsoft's "Windows [NT] everywhere" strategy.
by musicale
5/31/2026 at 7:13:10 PM
In addition to Xenix, there was apparently also a System V port for the Lisa.by musicale
5/31/2026 at 2:32:41 AM
That delay in shipping a memory-protected Mac was probably originally at least as much the result of upper-management politics as anything else. After Jobs left Apple Gassée cancelled Jobs’ pet project, the Big Mac which was intended to run Mac applications on a Unix base. Big Mac project leader Rich Page (and IIRC some other project members) rang Steve Jobs begging him to do something, and the rest is history.by leoc
5/31/2026 at 5:37:35 AM
Or fully embracing the Pascal programming model.I think it was in one of the On the Metal interviews where one of the guests mentions MPW was a submarine project, from UNIX background engineers, to eventually replace Pascal with C++.
by pjmlp
5/31/2026 at 7:17:21 PM
Well they did exactly that - rewriting the Finder in C++, etc.But it's unfortunate that losing Pascal/Object Pascal also meant losing bounded strings and array bounds checking, even if people turned the latter off in the 1980s because they thought that the performance cost wasn't worth the reliability improvement. That was probably the wrong trade-off then (at least for most regular application code) and even more so today (especially for the vast amount of legacy C code.)
by musicale
5/31/2026 at 12:34:46 PM
Yes, but that could be problematic given the memory constraints of that time:https://www.folklore.org/Puzzle.html
To this day, one of my favourite word processors is WriteNow, which was ~100,000 lines of assembly.
by WillAdams
5/31/2026 at 1:20:50 PM
Why is writing inline Assembly considered an advantage of C, a language extension even not part of ISO, and always used to point out issues when other languages make use of it?Naturally there had to be a balance, until mid-90s what we consider AAA games, were mostly Assembly.
by pjmlp
5/31/2026 at 1:41:51 PM
I didn't mention C.The observation was that linking in the Pascal library was problematic when one was storing everything on a single 400KB Micro Floppy.
by WillAdams
5/31/2026 at 1:59:28 PM
It was implied from my previous post, the story regarding size and the reference to Assembly.Sorry if misunderstood.
by pjmlp
5/31/2026 at 1:03:06 AM
> certainly would have led to a path where Macintosh was just another abandoned experiment like the Apple III.This seems really extreme. You're saying a trackpad would have made the whole thing a failure?
by asveikau
5/31/2026 at 10:35:41 AM
I'm saying that being designed around the singular task of word processing would have made it a platform/ecosystem failure, even if was a nominally successful one-off product.The Macintosh (specifically the original 128k version) was a dismal market failure too. What succeeded (relatively speaking) was the platform/ecosystem.
by simondotau
5/31/2026 at 2:57:27 PM
Even the 128k was reasonably successful commercially. Hundreds of thousands of units sold, which was quite good for the time. Inflation-adjusted, it cost quite a bit more than the Vision Pro. They sold the same model with very minor revisions (512, then 512e) into mid-1987.The 1986 Macintosh Plus was a huge market success and it is only modestly different from the original. Even the SE and Classic didn't change things much.
by rjrjrjrj
5/31/2026 at 12:05:46 AM
Part of this was due to Steve Jobs insisting on no arrow keys on the O.G. Mac's keyboard so as to force usage of the mouse.by WillAdams
5/31/2026 at 3:31:08 AM
Jef's vision for a high volume appliance computer was eventually realized in the Canon Cat which he co-created with Canon. https://en.wikipedia.org/wiki/Canon_CatVision may spark greatness, but execution is what makes it real. The Hacker News crowd can debate endlessly about who conceived the Macintosh while dumping on Steve Jobs.
But Steve Jobs did what ultimately mattered: he shipped.
by jnaina
5/31/2026 at 12:15:35 PM
But the part that should not be forgot is Jef Raskin’s book The Humane Interface. Many of the ideas in the book are only now implementable with the arrival of AI.Also he defined the difference between computers and humans as computers been precise and accurate and humans as vague, but more flexible. We have now had a paradigm shift in that ai is now the flexible interface that sometimes hallucinates.
by uxhacker
5/30/2026 at 8:29:17 PM
That was my exact thought when I read the submission’s title. Thank you for finding and posting the article.This interview does seem to have a comment about it:
> Andy [Hertzfeld, a major developer on the early Mac team], unfortunately, has not generally gone back to the original documents, and he’s interviewed lots of people about the history of the Mac, but not me. His website is, as a result, full of errors.
by latexr