I must say that already in the early 2000s web developers were tired of hand-coding everything, and many sought some sort of automation -- a framework, a CMS. Already in 2004 I made a site with barebone approach -- put a txt in a diretory tree and let PHP simply add tags instead of linebreaks and insert it into HTML. The alternative those days was a heavy content management systems. And I came to Django after two awful PHP frameworks, written by lead developers at the workplaces. So, frameworks like Django were a more gradual transition, and they were much more pleasant to work with.

Sure, as you pushed it further, like add versioning to objects, things got very tricky and not guaranteed to work, and no way to fix.

But otherwise, yes, the attitudes look similar.

On the other hand, using frameworks later on was a good attempt to standardize things. Having some homegrown GUI nobody knows how to work with isn't an advantage either. Personally I refuse things that "feel" too big (Nuxt/Next), but like Vue... Currently though, I want to get rid of most Javascript so I'll work my way to HTMX or Alpine type solutions with server side templates. Personally the less tech I use the better, there was a time where you had all kinds of bullshit in a web app prior to even adding a single line of custom code.