3 ms·
If you use htmx you have to implement something server-side to return HTML, where most frameworks return JSON. Also, idk how you would handle form validation or
by armchairhacker 5y ago
If you use htmx you have to implement something server-side to return HTML, where most frameworks return JSON. Also, idk how you would handle form validation or authentication. And what if you have to transmit something that needs to be in JSON? Then you need another client-side api.
In general the issue with small frameworks is that you need 5 of them then still implement a lot yourself. Vs a big bulky framework which takes time to really learn, but has integrated support for all the features you need.
It’s why many people use big game engines instead of making games from scratch. If you make a game from scratch you need to implement asset management, rendering, animation, collision detection, AI, and export to multiple platforms. Game engines have built-in support for all of these things.
And i do know that many people use static sites or simple blogging platforms. Most sites i visit are actually pretty simple and look like they were built on older technology. On the other hand, Facebook, Twitter, YouTube, etc. kind of need to use complex frameworks because they’re complicated apps.
- recursivedoubts 5y agoauthentication is trivial and session cookie based, as was common before JSON-based apps became the norm. all mature web frameworks have this form of authentication baked in or available as a standard library. validation is also trivial: you do can do it server side as was normal for many years. htmx also allows you to plug in to the HTML5 client-side validation API if you'd like: https://htmx.org/docs/#validation https://htmx.org/docs/#validation there is no need for a complex front end framework for the vast majority of web applications. something like twitter or gmail could easily be built using a hypermedia-oriented approach, but when they were built hypermedia hadn't been advanced in nearly two decades. now it has.