lol, this video is blowing up (relative to my channel). Just want to re-iterate my point that I make in the end of the video (starting from 12:15), having an easy and fast way to create experiences that can compete with solutions that require "real frameworks" is a good thing. If HTMX allows crusty backend people to quickly create a solution that actually works better than most UI that is created by "a real framework" (it could be Vue, could be React, could be Svelte, Angular, whatever), then it will push "real frameworks" to create better baseline and better libraries to compete with HTMX. And that's a good thing because the main people who win are the users getting better UX.
crusty backend people? dude, it is you the frontend people who make websites horrible to use because you have abused all the technologies in the browser, since the 1990s, you abused frames, then abused flash, then abuse javascript. And the only result is terrible UX, I mean you people can't handle a simple single threaded runtime while backend are handling the whole show.
I've found HTMX + Alpine JS to be a nice/fun combo(working mostly in vue in my dayjob), for both hypermedia and having a store/state + other spa-like behaviors (and good ol' data handling if needed). Not saying I'd recommend our clients to switch, but for hobby projects and when I'm playing around trying to learn with Python/Rust/whatever on the backend, I like it.
So, not sure if I'm a backend guy but I do like the idea of HTMX for some things. I have written a kind of media center app where I was using React + Babel (Client side transpliling I believe is what it's called) as part of a blend between it and regular JS to handle reactivity. HTMX just fits my needs better than what I was doing with React on a small scale. The biggest problems I've got with it are the idea that if the server handles state for every client or just pushing a lot of HTML that could/should be handled by the client. Technically server is the ultimate state or final state but there's this in between in my mind where client is better suited that doesn't affect the authority of the server but has it's own authority space. Anyway, not sure if what I said makes sense but... meh.
Yeah, I would definitely agree that most apps will need both, server interactions and client interactions. In HTMX they recommend use "locality of behavior" to make amount of stuff that you need to change/send smaller
Why the hate for Vue? Doesn’t the argument about the select, apply to react and all other frontend frameworks? You can write badly-accessible components anywhere :D
yeah, the Vue thing just happened to be the example from kick that I was thinking about :) it could have been many other ones :) worked for the thumbnail though 😅
There's a class of things that you can only do with React/Solid and I like to use the right tool for a job :) BTW, I have another video about HTMX on my channel that is longer than this one and covers my thinking a bit more :) ruclips.net/video/fcupfjeZwCE/видео.html
You’re not articulate enough to take this position, let alone even blend comedy 🎭 i think you’re in a very isolated middle ground between knowledgeable about web dev and your ability to communicate. Also you’re hashing old topics all the larger streamers cover to a nauseating degree, maybe try objectivity to stand out.
lol, this video is blowing up (relative to my channel). Just want to re-iterate my point that I make in the end of the video (starting from 12:15), having an easy and fast way to create experiences that can compete with solutions that require "real frameworks" is a good thing.
If HTMX allows crusty backend people to quickly create a solution that actually works better than most UI that is created by "a real framework" (it could be Vue, could be React, could be Svelte, Angular, whatever), then it will push "real frameworks" to create better baseline and better libraries to compete with HTMX. And that's a good thing because the main people who win are the users getting better UX.
crusty backend people? dude, it is you the frontend people who make websites horrible to use because you have abused all the technologies in the browser, since the 1990s, you abused frames, then abused flash, then abuse javascript. And the only result is terrible UX, I mean you people can't handle a simple single threaded runtime while backend are handling the whole show.
I've found HTMX + Alpine JS to be a nice/fun combo(working mostly in vue in my dayjob), for both hypermedia and having a store/state + other spa-like behaviors (and good ol' data handling if needed). Not saying I'd recommend our clients to switch, but for hobby projects and when I'm playing around trying to learn with Python/Rust/whatever on the backend, I like it.
I agree. It's a great combo. Have you figured out Alpine's reactive methods? I can't find nothing on it
bread santa giving his opinion
"Htmx is like jQuery"
"I don't understand what the fuck htmx is"
Spot the difference
HTMX is not as powerfull as VUE or REACT but very usefull when you use template like django for example (you dont need to write javascript).
So, not sure if I'm a backend guy but I do like the idea of HTMX for some things. I have written a kind of media center app where I was using React + Babel (Client side transpliling I believe is what it's called) as part of a blend between it and regular JS to handle reactivity. HTMX just fits my needs better than what I was doing with React on a small scale. The biggest problems I've got with it are the idea that if the server handles state for every client or just pushing a lot of HTML that could/should be handled by the client. Technically server is the ultimate state or final state but there's this in between in my mind where client is better suited that doesn't affect the authority of the server but has it's own authority space. Anyway, not sure if what I said makes sense but... meh.
Yeah, I would definitely agree that most apps will need both, server interactions and client interactions. In HTMX they recommend use "locality of behavior" to make amount of stuff that you need to change/send smaller
Why the hate for Vue? Doesn’t the argument about the select, apply to react and all other frontend frameworks? You can write badly-accessible components anywhere :D
and yes, I got baited for the thumbnail
yeah, the Vue thing just happened to be the example from kick that I was thinking about :) it could have been many other ones :) worked for the thumbnail though 😅
im listening
so you love bloated React?
There's a class of things that you can only do with React/Solid and I like to use the right tool for a job :) BTW, I have another video about HTMX on my channel that is longer than this one and covers my thinking a bit more :) ruclips.net/video/fcupfjeZwCE/видео.html
Free Ukraine.
You don't understand HTMX. 🧐
React developers think that their library is best 🤣
You use Astro 😶
I understand some of those words. Just not in this particular order!
@@ParasocialFix 😭😭😭
I hate HTMX because it's like I put graffiti on random wall on berserk. It's hard to ensure the swap/insert doesn't change/conflict other swap/insert.
Yes, you have to maintain the "locality of behavior", otherwise it will go pretty bad pretty quickly :) htmx.org/essays/locality-of-behaviour/
You’re not articulate enough to take this position, let alone even blend comedy 🎭 i think you’re in a very isolated middle ground between knowledgeable about web dev and your ability to communicate.
Also you’re hashing old topics all the larger streamers cover to a nauseating degree, maybe try objectivity to stand out.