Live data from Hacker News

Htmx is part of the GitHub Accelerator

htmx.org

151–160 of 520 posts

Re: Htmx is part of the GitHub Accelerator

#151

I've been a HTMX fan "since before was cool".. Very happy for the recent attention and "success". Also enjoying the shitposting and backlash mostly from the front-end crowd who believe the Web was invented in 2013 and they "made that city". :) I'm biased since the time Backbone.js came around, I understood part of the pain but was moderately skeptical, fast forward to React with the young energetic bros building dead…

React is very diverse community, who are these react bros? I went to a series of JavaScript conferences and React is extremely diverse.

I was recounting the past. I'm sure it is "diverse" ( whatever that means ) now because it became kind of a industry standard for front-ends.

Good to see diversity all around, I just wish there also would be diversity of thought and it comes to building web pages. But I guess that would lead to people admitting ~80% of all the stuff they build does not require React or equivalent js frameworks and that would be both an ego and economic/résumé problem..

Re: Htmx is part of the GitHub Accelerator

#152

Great news. I have had good success and a rewarding experience using htmx the past year. It has been so great in tandem with Clojure using hiccup for SSR. Once htmx clicks for you, you are almost left stunned by how simple and flexible it is. You can't believe that this isn't how HTML evolved to as a hypermedia. It becomes very obvious that this is how web development should have evolved. I hope someday that what htm…

> It becomes very obvious that this is how web development should have evolved. I have to disagree with that. I’m happy htmx exists and that it works for many but in my professional life I've found few cases where it's the best choice. And that’s fine! It’s a wonderful thing that the web has been able to grow in so many diverse ways, there should be no one way it “should have evolved”. IMO this is the biggest mistake…

I'm kind of guessing / reading into their comment here but. Using htmx doesn't give me the feeling of "this is the only way I ever want to do this" but more "if html worked like this I wouldn't use js most of the time." The sense that an opportunity was missed and now we're paying for it in complexity.

Re: Htmx is part of the GitHub Accelerator

#153

Earlier quoted context omitted.

as a primarily backend dev I really don't see the appeal here. So now I need to make endpoints for every little UI element that I want to be updated by user interactions? And somehow keep it styled and matching all of the UI elements rendered on the frontend? No thanks, I'll just give you data and you can present it however you please.

> So now I need to make endpoints for every little UI element that I want to be updated by user interactions? No. Htmx supports extracting a subset of received HTML and merging it with the current page. So, for a typical form, you _could_ do a request to validate the entire form then extract the relevant error message for the input field that triggered said request. This would re-use most code of the actual form subm…

Could you link to an example on extracting parts of the form? I have a feeling I'm using way to many routes to handle every specific case!

Thanks.

Re: Htmx is part of the GitHub Accelerator

#154
post #109
post #12

The twists and turns my career has taken had me pretty much skip the whole front-end JavaScript framework wars so it's nice to see "plain old HTML" make an enhanced comeback.

The site and it's examples do not work with JavaScript disabled. This is a regression on graceful degradation.

That's a shame, and bad use of htmx, these examples shouldn't be showcase examples.

It takes careful but not extraordinate thinking to think of ways to get consistent results with or without JavaScript turned on. Indeed, when a visitor hits a site for the first time they get the full response so everything for a graceful degradation should already be there to use. If I can figure it out, I'm sure big CS brains can.

Re: Htmx is part of the GitHub Accelerator

#155

Earlier quoted context omitted.

> It becomes very obvious that this is how web development should have evolved. I have to disagree with that. I’m happy htmx exists and that it works for many but in my professional life I've found few cases where it's the best choice. And that’s fine! It’s a wonderful thing that the web has been able to grow in so many diverse ways, there should be no one way it “should have evolved”. IMO this is the biggest mistake…

I'm kind of guessing / reading into their comment here but. Using htmx doesn't give me the feeling of "this is the only way I ever want to do this" but more "if html worked like this I wouldn't use js most of the time." The sense that an opportunity was missed and now we're paying for it in complexity.

The complexity is just shifted around from JS to HTMX (or hypothetically, html). Not a noticeable improvement.

Re: Htmx is part of the GitHub Accelerator

#156

Earlier quoted context omitted.

There was already a pretty good non-trivial real-world example where a company replaced their entire React site with htmx and got impressive results: https://htmx.org/essays/a-real-world-react-to-htmx-port/

Where is the source?

There's literally a talk linked to in the essay.

Re: Htmx is part of the GitHub Accelerator

#157
post #47

Earlier quoted context omitted.

I hear you're buying a synthesizer and an arpeggiator and are throwing your computer out the window because you want to make something real. I hear that you and your band have sold your guitars and bought turntables. I hear you rewrote your http endpoints to return JSON because that was REST. I hear that you and your band have sold your turntables and bought guitars. I hear you rewrote your http endpoints to return t…

Is this some kind of metaphor?

https://genius.com/Lcd-soundsystem-losing-my-edge-lyrics

Re: Htmx is part of the GitHub Accelerator

#158

Earlier quoted context omitted.

Had an heated debate with someone that was really angry at everything react, for good reasons, but being oblivious that htmx can't replace client side logic. React hype + backend crowd I guess.

as a primarily backend dev I really don't see the appeal here. So now I need to make endpoints for every little UI element that I want to be updated by user interactions? And somehow keep it styled and matching all of the UI elements rendered on the frontend? No thanks, I'll just give you data and you can present it however you please.

No, you just submit the form like normal and redirect (via htmx) to a success page, or return errors using out-of-band updates in the response.
Post reply on HN