[mwnorman2]

Well, I DID live through that era and I AM the 'old-man-yelling-at-clouds' ;-) and the main issue was that getting Smalltalk developers was a HUGE headache. I worked for a Telecom company (Canada's largest, rhymes with 'Ortel') and we needed to develop our own courses - yours truly developed and delivered dozens of hours of training.

This lead to some extraordinary per-diem charges that I knew some folks enjoyed for a while, mostly paid for by the Financial industry. Eventually those on the paying side looked for cheaper alternatives .. and yes, the new-kid-on-the-block Java played a big role, but so did Visual Basic!

[igouy]

'We read and heard many stories about confident and experienced programmers plunging into self-study tutorials, only to give up in frustration after several hours, still wondering, "Where is the application code?" The object paradigm, in which program control is distributed across a set of tightly encapsulated and high-function software objects, was alien to experts in procedural design.

… to use Smalltalk fluently, a programmer must become familiar with a huge class hierarchy and with the tools of a sophisticated interactive programming environment. New programmers often became lost in the hierarchy or spent considerable time in unfocused exploration of the interactive tools.'

"Making Use: scenario-based design of human-computer interactions", 2000, page 103

https://www.google.com/books/edition/Making_Use/s-0ZuadhBBAC...

[em-bee]

doesn't sound much different than studying the class library of any other language.

[igouy]

The past is a foreign country …