Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

htmx

htmx.org

Post reply on HN
Print view View original

181–190 of 291 posts

Re: htmx

#181

Post by sroussey »

leidenfrost wrote: post #135
marcus_holmes wrote: post #98

Earlier quoted context omitted.

The "new hotness" only matters if you're going to try and get a job as a FE dev in a large team. The "old hotness" still works, and likely has the more obscure bugs worked out of it. And you can always just write the thing in JS without any hotness at all. The JS ecosystem's obsession with frameworks is a diversion. You really only need a framework if your site is super complex. And even then, if you're careful about…

This. 90% of the toolchain is not required at all. Just quality of life improvements. Good ES6 (and TS) idiomatic code feels actually closer to reading Scala than reading a legacy Jquery app. And the V8 engine has so much investment in optimizations today that is actually closer to Java and in some cases lighter than Go. IMHO people don't hate JS in reality. They hate the strawman made of the worst parts of Junior co…

Same could be said for php…

Re: htmx

#182

Post by markmark »

kkapelon wrote: post #150
julianeon wrote: post #138

Earlier quoted context omitted.

I think this comment is a bit out of date, especially if you’ve been watching JS from a distance for the past couple decades. This would’ve been true circa 2014. In 2023 it’s obsolete. There’s one framework that won, that’s all you have to learn, as far as the industry goes (as opposed to hobbyists) it’s been decided. React won. React is the framework you learn. “Popular frameworks for the past 6 years” - React has b…

> React won. React is the framework you learn So nobody should learn AngularJS any more?

Nope.

Re: htmx

#183

Post by markmark »

alex_lav wrote: post #140
zackify wrote: post #127

Earlier quoted context omitted.

I’m over here continuing to use react for 9+ years but every post on here acts like it’s changing every day.

Classes? Components as functions? Classes again? Hooks?

Classes still work fine if you want to keep using them.

Re: htmx

#184

Post by zelphirkalt »

brabel wrote: post #158
number6 wrote: post #134

Earlier quoted context omitted.

Do you still use gulp or is it webpack nowadays?

You're outdated. Everyone is using Parcel now.

Funny, how even the sibling comment states something different. Maybe there are a lot of bundler bubbles in the JS world?

Re: htmx

#185

Post by mekoka »

TekMol wrote: post #121

Hmmmm... no. This: Click Me Should be just this: Click Me This way, no magic would be needed, a lot of indirection and complexity would be avoided and everybody who knows HTML and JS could immediately read and understand it: - When does something happen here? When the button is clicked. - What does happen? htmx.post() is called.

> no magic would be needed, a lot of indirection and complexity would be avoided

Is this an informed criticism based on your experience having worked with htmx, or is it just an off the cuff opinion?

Personally, I don't think the goal should be "no magic", or "no indirection", or "no salt", or no "sugar". I feel that aiming for just the right amount of those things, to have the goody without crossing over to disgust, is a sound goal.

Re: htmx

#186

Post by listenallyall »

creatable wrote: post #147
listenallyall wrote: post #137

Earlier quoted context omitted.

React isn't the only way, of course, but it's likely the most popular. Why do you consider Vue or Svelte to be valid alternatives but not HTMX, despite plenty of people endorsing it and openly proclaiming how successful it's been in their projects?

I personally do consider HTMX to be a valid alternative to React, but I also think that a lot of usage / promotion of it comes from people who are misinformed and think that the entirety of the JavaScript ecosystem is React. I consistently see a lot of people use HTMX over React alternatives purely because of a "distaste for JavaScript" or an understanding that everything is or has to be as complex as React unless yo…

If people are "misinformed", that's a marketing fail by those other frameworks, despite many years of headstart. How are people even finding HTMX (with a single developer and until very recently, no corporate support) in a marketplace which includes Angular, backed by Google?

Or maybe people are kinda informed, and simply drawn to HTMX because it's easier to learn than Vue, Svelte, Mithril, Cycle, whatever (or they just don't want to try a zillion frameworks) and it works really well and developers seem to love it and recommend it a lot?

Re: htmx

#187

Post by loveparade »

mkesper wrote: post #110
loveparade wrote: post #99

Earlier quoted context omitted.

htmx is another tool just like that, another goalpost in the frontend webdev world. It's just happens that the most recent hype is "don't write JS", but fundamnetally it's no different. Just another framework/library that has gotten some traction. In a few years we'll be back full cycle and it will be in vogue to write JS again, probably because htmx and associated projects have grown to complex.

A key difference is the promise to be working even without JavaScript.

It's no different from anything else. The promise if every framework is to abstract away some low-level details. Whether that means writing "higher-level JS" like jQuery did many years ago already, and hundreds of other frameworks do today, or inventing some new DSL like htmx does that translated to JS internally. No difference.

Re: htmx

#188

Post by the_gipsy »

emodendroket wrote: post #165

Seems like a horrible idea that totally breaks separation of concerns, so I’m sure it will be a huge success you’ll see everywhere very soon.

There are multiple ways of separating concerns. Htmx is faithful to the original HTML separation of structure / presentation / behavior. Elm cuts this way too but with a completely different approach. React does components.

Pick your poison because in any case there will be crossing of those concerns.

Personally I've never seen react code that doesn't go sour beyond a toy demo.

Re: htmx

#189

Post by creatable »

listenallyall wrote: post #186
creatable wrote: post #147

Earlier quoted context omitted.

I personally do consider HTMX to be a valid alternative to React, but I also think that a lot of usage / promotion of it comes from people who are misinformed and think that the entirety of the JavaScript ecosystem is React. I consistently see a lot of people use HTMX over React alternatives purely because of a "distaste for JavaScript" or an understanding that everything is or has to be as complex as React unless yo…

If people are "misinformed", that's a marketing fail by those other frameworks, despite many years of headstart. How are people even finding HTMX (with a single developer and until very recently, no corporate support) in a marketplace which includes Angular, backed by Google? Or maybe people are kinda informed, and simply drawn to HTMX because it's easier to learn than Vue, Svelte, Mithril, Cycle, whatever (or they j…

> or they just don't want to try a zillion frameworks

But isn't HTMX one of said zillion frameworks? What makes it any different?

Re: htmx

#190

Post by alex_lav »

markmark wrote: post #183
alex_lav wrote: post #140

Earlier quoted context omitted.

Classes? Components as functions? Classes again? Hooks?

Classes still work fine if you want to keep using them.

This doesn't appear to be what the docs recommend anymore, which is exactly what my (obviously flippant) post was meant to highlight.
Post reply on HN