Live data from Hacker News

Htmx Is the Future

quii.dev

601–610 of 875 posts

Re: Htmx Is the Future

#601
post #11
post #3

It's kinda funny to me that many of the "pros" of this approach are the exact reasons so many abandoned MPAs in the first place. For instance, a major selling point of Node was running JS on both the client and server so you can write the code once. It's a pretty shitty client experience if you have to do a network request for each and every validation of user input. Also, there was a push to move the shitty code fro…

I often work on an old ColdFusion application. It's amusing that for a long time the response was "oh man that sounds terrible". Now it is "oh hey that's server side rendered ... is it a new framework?". The cycle continues. I end up writing all sorts of things and there are times when I'm working on one and think "this would be better as Y" and then on Y "oh man this should be Z". There are days where I just opt for…

I often wonder if someday we could see WebObject or ColdFusion being open sourced.

Re: Htmx Is the Future

#602
post #134

Server-side apps cannot provide optimistic UI. No matter how you feel about it, they are limited in this capability compared to client-side apps. The user doesn’t care about the technology. For example, imagine a todo app that shows a new todo immediately. Or form validations that happen as soon as data is entered. That’s a superior experience to waiting on the server to continue interaction. Whether that’s harder to…

You don't have to be restricted to just using htmx, you can use it with client side Javascript to give you that interactivity you need in the places you need it. Indeed, the creator of htmx has created another library called hyperscript which he's described as a companion to htmx. https://hyperscript.org/

Awful. The last thing we need is another layer further away from plain javascript cluttering up web pages.

Re: Htmx Is the Future

#603
post #3

It's kinda funny to me that many of the "pros" of this approach are the exact reasons so many abandoned MPAs in the first place. For instance, a major selling point of Node was running JS on both the client and server so you can write the code once. It's a pretty shitty client experience if you have to do a network request for each and every validation of user input. Also, there was a push to move the shitty code fro…

> all the devs writing shitty MPAs are now writing shitty SPAs

drain the swamp man

Post reply on HN