Part of the issue is that "systems" are no longer designed holistically , and instead follow Conway's Law , which leads subcomponents to be designed in isolation and then combined as best as possible.
Systems programmers build the foundation of a software platform, without a clear vision of the end goal. They focus on the intricate details of the platform, but pay little attention to how this fits in the final product.
 maybe only at Apple, inheritors of Kay's approach?
The "high priests" line is a Bob Barton quote, which I believe probably dates back to the mid-sixties.
this might not always be possible but if you can reveal a powerful, clear metaphor (& oh my are good metaphors tricky to come by!) the resulting alignment is truly liberating.
Of course, even if someone knows they have a great idea and is willing to wait for it to flower, there's certainty that will happen in their lifetime.
Part of why the world "flew by" is because those ideas existed and informed what came next. And even today what he have falls short of many of those ideas (most modern dynamic languages are worse than Smalltalk in many if not most aspects for example, except adoption).
I also was sent a frank.image that runs on Squeak and uses these files but don't know where that can be found.
This HN post has links to many of the STEPS artifacts and their successors:
I think these are the ones I saw:
Sharing is important - we're all communication junkies
Anyone know what Alan Kay meant by this or have a pointer to an expansion?
The way it is implemented (hopefully) opens up the mind to how OO actually can work, but in practise, when you use if-else in Smalltalk, it's pretty much the same as in other languages.
Some aspects of this are elaborated in "Design principles behind Smalltalk": https://www.cs.virginia.edu/~evans/cs655/readings/smalltalk....