There is something to the existence of fads and fundamentals. When I started, it was Object-Oriented-Programming (with multiple-inheritance and operator overloading, of course), Round-Trip Engineering (RTE), XML, and UML.

IMHO, not the ideas were bad, but the execution of them was. Ideas were too difficult/unfinished/not battle-tested at the time. A desire for premature optimisation without a full understanding of the problem space. The problem is that most programmers are beginners, and many teachers are intermediate programmers at best, and managers don't understand what programmers actually do. Skill issues abound. "Drive a nail with a screwdriver" indeed.

Nowadays, Round-Trip Engineering might be ready for a new try.

Olin also wrote the greatest acknowledgment section ever: https://scsh.net/docu/html/man.html

I always recommend people to learn at least one of the following: scripting language, compiled language, bytecode compiled language (C# or Java are industry giants), and at least one front-end web language either TS or JS. If they're still hungry I explain Erlang / Elixir / Gleam and tell them to try that out.

> Java and its OO relatives capture a communications-oriented model of computation where the funda- mental computational elements are stateful agents that compute by sending one another messages;

I wish even only half the OOP world actually understood it as the above.