71–80 of 136 posts
Earlier quoted context omitted.
Actually this was just a stupid bug I introduced in 2.0.3 which was found soon after 2.0.3 shipped. I fixed a bug that allowed ajax api to target body and blow away your whole page in error if one of the selectors you pass in was not found. But It broke the default no source and target behavior but this is now fixed that 2.0.4 is shipped
This is why I think semver is impossible to do in practice.
Earlier quoted context omitted.
The creator of HTMX and Intercooler.js? I think they already know.
Both of them take this feud very seriously from what I've seen
Htmx belongs on a pedestal
Earlier quoted context omitted.
Actually this was just a stupid bug I introduced in 2.0.3 which was found soon after 2.0.3 shipped. I fixed a bug that allowed ajax api to target body and blow away your whole page in error if one of the selectors you pass in was not found. But It broke the default no source and target behavior but this is now fixed that 2.0.4 is shipped
This is why I think semver is impossible to do in practice.
The semver docs explicitly address this scenario. If a change in minor update breaks compatibility release a new minor update to revert the change.
Earlier quoted context omitted.
Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.
Imagine being this delusional
People who promote SSR are simply trying to rope frontend devs into their P2 or P1 incident responses and use them as whipping boys. This shit has to stop.
If you don't suspect your web devs are doing all kinds of cache-busting dog shit on your backend ruining your performance dude idk what to tell you other than: what year do you think it is and who do you think you hired?
It's SSR nonsense constantly spammed on sites like this that make you think it's a good idea and ultimately give inexperienced devs the green light to do all kinds of dumb shit that carries heavy technical debt once you need to meet an SLA that is more realistic than anyone who seriously uses HTMX on anything at that scale. There's no excuse for using tools like this other than ignorance.
Earlier quoted context omitted.
Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real.
Sick and tired of any server-side rendering of web pages. If you don't have to deal with incident response you can be quiet. It doesn't scale and it complicates meeting any client requirements. Get this trash outta here. For real. Ummm... do you know where you are? Do you know how this works? Hint -- try "view source" right now. I made it easy for you by pasting a random snippet above...
Earlier quoted context omitted.
and yet here we find ourselves, exchanging our server side rendered opinions on the matter
Each comment should be entered into the code then committed. That commit then should trigger the CI build. That should then upload the static assets to the CDN. It's clearly the optimal solution.
Do some people have examples of interactivity they were able to replace with Htmx? For me, I've been able to get turbo style links with the boost to get nice page transitions. I can also see how I could use the class-tools extension to enable buttons to open dialogs etc. I'm curious to see when people say they needed an SPA for interactivity, what interactive features Htmx can already do and when do we need to break…
But I want things like an on-site calculator. I load in products and prices, users can adjust sliders to change the quantity and relevant number is calculated. I don't want to use HTMX for this to call the server each time, I want instant reactivity and state in the frontend maintained so when the user has tweaked as necessary they can just check out.
HTMX does not fit this use case so I use React to build widgets (or if even more complex SPA then Angular). If I'm using a JS framework anyway, then I don't need HTMX. It's just something else to clutter the project and remember to use.
HTMX has its place but with the user expectation for reactivity in the browser I personally find it too limiting.