Live data from Hacker News

Htmx 2.0.4 Released

github.com

61–70 of 136 posts

Re: Htmx 2.0.4 Released

#61
post #16

Earlier quoted context omitted.

I'm wondering how they use this site

I wasn't talking about Hacker News or lobste.rs :)

So you were only trying to say that page refreshed aren’t common on some subset of pages where it isn’t common? What’s the point of that argument.

Also curious, why are you arguing so intensely for a “solution” that seems to only be worse and introduces issues as explained, without ever having stated any problem you are trying to solve with the change?

Re: Htmx 2.0.4 Released

#62
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 out some JS.

An example that I think needs JS is a copy paste button.

Re: Htmx 2.0.4 Released

#64

> Calling htmx.ajax with no target or source now defaults to body (previously did nothing) This one jumped out to me as an interesting one for a patch release. Changing the default behavior feels like a breaking change, though hopefully there weren't sites expecting an ajax call to not do anything.

> Changing the default behavior feels like a breaking change I'm fine with breaking changes personally. An adherence to maintaining backward compatibility always is what leads to bloat and criticisms of "poor design" from HNers in the future. Keep it slim, have one way to do things, and avoid the disaster that is js and python today.

I'm not fine with breaking changes in a patch bump, otherwise it means versioning is useless

Re: Htmx 2.0.4 Released

#65

So happy every time I see HTMX. I'm hoping there is more innovation in this space with React engineers rediscovering the benefits of server-side rendering and Backend-For-Frontend efforts. I think the perfect stack involves all 3 paradigms (initial loads, hypermedia loads and data/AJAX loads) used in parts of the application as makes sense.

> React engineers rediscovering the benefits of server-side rendering and Backend-For-Frontend efforts

React 19 has just been released recently with server components and server actions. Worth having a look. It's a very powerful model.

Re: Htmx 2.0.4 Released

#66

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…

One thing I use HTMX for is to quickly hack interactivity into a more traditional site.

One example is incremental filtering: I added an input field, and made it (a few ms after the last value change) load the same page the user is already on with a query parameter that filters the items in the response. Then I just replace the list of items with the contents from the response, ignoring the rest of the page.

It's a bit wasteful perhaps, but all this took just a few lines of HTML.

Re: Htmx 2.0.4 Released

#67

> Calling htmx.ajax with no target or source now defaults to body (previously did nothing) This one jumped out to me as an interesting one for a patch release. Changing the default behavior feels like a breaking change, though hopefully there weren't sites expecting an ajax call to not do anything.

> Changing the default behavior feels like a breaking change I'm fine with breaking changes personally. An adherence to maintaining backward compatibility always is what leads to bloat and criticisms of "poor design" from HNers in the future. Keep it slim, have one way to do things, and avoid the disaster that is js and python today.

In addition to what the siblings say, in case parent isn't aware of semantic versioning: https://semver.org/

Re: Htmx 2.0.4 Released

#68

> Calling htmx.ajax with no target or source now defaults to body (previously did nothing) This one jumped out to me as an interesting one for a patch release. Changing the default behavior feels like a breaking change, though hopefully there weren't sites expecting an ajax call to not do anything.

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.

Re: Htmx 2.0.4 Released

#70
post #50

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

Is this supposed to be a joke? If it is... it isn't funny. If it isn't... Maybe it's time to face the fact that you're very wrong about this...
Post reply on HN