I love this sort of thing. Whenever I try to make a case for anything at work, I always try to frame it in a historical context because everything we do in comp

I love this sort of thing. Whenever I try to make a case for anything at work, I always try to frame it in a historical context because everything we do in computing exists on a historical timeline that's relatively short and ongoing and we shouldn't necessarily hold anything as a universal truth. It's possible that everything we hold dear (OOP, etc) will be a blip in early computing history in the grand scheme of things. I work in web so one thing I preach a lot is that a lot of the explosion of activity in JS over the past decade or so can largely be traced back to the introduction of the iphone, the subsequent mass adoption of mobile devices, and the sudden expectation for native-app like experiences from the web on low powered devices. Thus, a lot of notions about javascript that persist from pre mobile, pre es6, etc need to be checked. "Javascript framework of the week" cynicisms tend to persist from a brief period of "throwing stuff at the wall" to figure out how to leverage AJAX to achieve SPA. Now the language and its ecosystem has matured tremendously and there are other problems to solve so it's important to constantly renew our perceptions and biases. Here's a js timeline I threw together recently https://time.graphics/editor/649085 https://time.graphics/editor/649085