Find me a modern US exec willing to actually invest in a risky hardware prospect, rather than throwing a billion dollars into real estate or "content" that can be filled with ads.
Considering how Intel doesn't tend to hold grudge-matches with their customers, I seriously doubt there was any risk in the first place. If TSMC yields were too low to mass-produce Apple Silicon, they could easily ship out another copy-paste Macbook iteration with Magic Keyboard and nobody would care what chip it had inside.
With the benefit of hindsight, it feels more like Intel and Apple were in a race to see who would outsource the Mac chip first. Since Apple already had the supply chain set up for the iPhone, cutting Intel out of the equation was mostly just a matter of designing an SOC. They took the opportunity, and now we're seeing Intel glumly admit that they too can be energy-efficient if they swallow their pride and pay TSMC.
I moved across the world (from Perth, WA) to work on open source software with some of my heroes (Bud Tribble, Andy Hertzfeld, Susan Kare) at Eazel. It was only a short time run, but I'm still in the Bay Area, still friends with many of the people I met there.
And I still use the software that I worked on at Eazel most days, which I can't say for anything I worked on since then.
What happens when the community decides this one isn’t good enough and comes up with a replacement? The problem I’ve always had with these descriptive names is (a) they are often hard to google because they conflict with all sorts of documentation about the problem space and (b) when they’re deprecated, they become a trap for beginners. “Cute” project names are better for the same reason as we don’t name children and pets random English phrases describing them.
Imagine if this happened with stream processing systems: “here at Acme Corp we decided that Apache Stream Processing wasn’t nearing our needs so we switched to Apache Creek Processing after evaluating it and Microsoft’s River Processing solution”
Yep, AFAIR he intentionallyed a scheme twice, but both times, the suits had a different idea (first time around, to ride on Java marketing; second time around, to compete with Microsoft and JScript).