3 ms·
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 adopt
by sergioisidoro 5y ago
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.
- wpietri 5y agoOoh, thanks for these pointers. Those are very interesting.
- Taurenking 5y ago+1 on HTMX and Alpine, wish they were more heavily advertised as an option for rapid prototyping MVPs or proof of concepts. No need to whip out React for an spa or Next(?) for a "server side rendered reactive frontend" (this concept in particular is weird to me as it pretty much means we've come full circle)
- iwebdevfromhome 5y agoDjango unicorn [0] looks like an interest concept too, similar to the htmx approach. [0]: https://www.django-unicorn.com/ https://www.django-unicorn.com/