I'm gonna go back a short bit and say, for me? Ruby on Rails. In 2007 I was plugging away at PHP with whatever frameworks were around at the time -- the vast majority of web dev that I saw then was pure procedural scripting down the page, maybe some `include` statements to pull in database functions. Especially in PHP, which encouraged mixing logic and HTML. The consultancy I was with had built custom stuff on top of…
I’m curious what your take is on the JAMStack+lambdas style of app development. I am working on a new web app. Initially, Elixir/Phoenix was looking like an excellent option, but then I looked at hosting and decided it would be easier to use something like the Serverless framework for AWS deployment which JAMstack+lambdas seems to match better — no need to manage VMs and networking infrastructure, mostly.
I'm a big fan of rendering majority on a server and then shipping it, especially with Phoenix's LiveView which allows you to write reactive UI without writing Javascript.
But I said it in another comment: shipping value beats everything. If you can ship quickly and effectively in JAMstack to lambda, don't let anyone tell you that's wrong.