[l0rn]

Yeah it's funny... Now 10 years+ in the web dev business. I occasionally got drawn by the hype, dug myself considerably deep into express based frameworks, sails.js, koa.js, nest.js... But in the end i had to conclude, my first go-to framework django always came out superior in terms of developer productivity. It even eventually covered the bases where i still thought node was superior like async/websocket communication. Imho Django and similar batteries-included frameworks are as state-of-the-art as they've ever been.

[sergioisidoro]

Especially if you couple it with HTMX / Alpine.js you get a really good stack that covers all the dynamic page updates people are getting used to, without adopting massive frameworks.

I just started with HTMX and so far I think it's really promising. Similar things happening with Rails and Hotwire.

It took a while for these frameworks to accept that JS and the frontend are also important aspects of the stacks, and hard to avoid if you want to build modern applications. But now that they're picking up, heavy JS frameworks start making less sense.

[iwebdevfromhome]

Django unicorn [0] looks like an interest concept too, similar to the htmx approach.

[0]: https://www.django-unicorn.com/

[wpietri]

Ooh, thanks for these pointers. Those are very interesting.

[airstrike]

It's called "the web framework for perfectionists with deadlines" for a reason!

[oaiey]

I have the same feelings about ASP.NET Core. I think everyone trends back to his reasonable sized home.

[antoniuschan99]

At my first job we were migrating from Coldfusion to Java. This Middle Aged Sri Lankan guy refused and only worked on ASP.NET. Much respect to him! He knew what he was comfortable with - and most likely looked at Java in disgust the same way Java folk would look at ASP.NET :P