The situation seems to have been similar in Sun Microsystems around the same era: a number of different high-level language/runtime projects kicking around (eg. Self), and a generally deflating outcome.
> While it was canned when Steve Jobs returned
I don't know enough about OpenDoc to comment about the merits of what happened, but here are a few things. First, Jobs and Apple were pushing Rhapsody (Cocoa as a cross-platform API for applications) https://arstechnica.com/staff/2008/04/rhapsody-and-blues/ when OpenDoc was cancelled. It's easy to see the cancellation as the ex-NeXTers killing anything that competed with the NeXT technology or just didn't particularly integrate with it. OTOH, OpenDoc was definitely seen as a big commercial and consumer-adoption flop before Jobs killed it. Finally, it has to be noted that OpenDoc's inspiration and competitor OLE is still around, perhaps underloved.
It was the time when Apple APIs went completely overboard in the amount of code required to do /anything/; OpenDoc was incredible in it's complexity; but even something like OpenTransport was fantastic amount of work to do anything simple -- especially compared to BSD sockets!
AppleScript was another one, being 'scriptable' was a lot of work, but being 'recordable' was a complete nightmare, and implementing the most complex language clauses was borderline suicide, the 'whose' clauses were amazing in their complexity for a feature absolutely nobody would use.
But, still, I miss Classic -- I think there was a lot of good that was thrown with the bath water when OSX arrived; sure, the underlying got a serious upgrade, but the user interface and anything associated got a serious downgrade, to this day really. I think the modern Finder is abhorrent, the Classic Finder was a beauty of consistency and ease of use in comparison. Yeah sure you got a couple of gadgets, that's it.
Honestly, the “component software model” had at least hundreds of millions of dollars in development thrown at it by all the major players and went essentially nowhere at the application level.
It had some nice architectural properties for developers, and COM at least has had a long and prosperous history as a building block. But it’s hard to imagine any possible world where business or consumers spent a significant fraction of their software dollars on components rather than full applications. So Steve was probably right.
The four and a half minutes prior are interesting (thoughtful introduction, Jobs' framing of the session and his brief thoughts about Apple's current position), but what he says in response to the questions following the OpenDoc question is deeply thought-provoking.
Many of the ideas Jobs shares show the general shape of recent and current Apple business decisions macOS and iCloud, for example. Especially interesting are his discussions of NIH syndrome, networking, and more.
Thanks, twoodfin, for pointing to this session which punctuates Jobs' return to Apple the year previous.
After all, the network is the computer.
Instead the GNU/Linux wars replaced the UNIX wars, and while GNOME and KDE do strive to provide that experience, everyone is using Electron apps instead.
The closest to that MacOS development experience turned out to be Android, where the actual kernel being used is irrelevant to user space.