The State of HTMX (2024)

Рет қаралды 9,069

Күн бұрын

Пікірлер: 35

@Jeff-co. 3 ай бұрын

Very interesting how HTMX's concept of what HTML should've naturally evolved into in time, and that it came out not long ago really, is competing head on againts all these big JS frameworks of years. Definitely a fan of it and cant wait to see everyone using it and take down all these complicated SPA frameworks!

@depafrom5277 3 ай бұрын

I wont be joining 😃

@Jeff-co. 3 ай бұрын

@@depafrom5277 That's cool. Any one can stay in their blind bubble of never ending JS frameworks and breaking changes. It's a nasty cycle honestly. But if you must, Svelte is the best one. I, on the other hand, and like many others, prefer progress and making my life easier as a developer 😅

@Jeff-co. 3 ай бұрын

@@depafrom5277 That's cool. Any one can stay in their blind bubble of never ending JS frameworks and breaking changes. It's a nasty and tiring cycle honestly. I, like many others, prefer progress and making my life easier as a developer 😅

@XboxTheBeatboxer 3 ай бұрын

I'm subbed for htmx and htmx-adjacent topics.

@jefferymuter4659 2 ай бұрын

I use htmx at our company in several production projects. Love adding as much html & css & js into the template to make things nice and readable.

@bambanx Ай бұрын

Can you use with an rest api? Its solid ? Thanks you

@vab7265 8 күн бұрын

@@bambanxi dont think is meant to be used with a rest api. There are some some limitation in calling http method other than POST and GET. Better to be seen like a shorthanded version of libraries like jQuery in order to handle and put the contet where is needed. Its not a replacement for SPA frameworks

@StingSting844 3 ай бұрын

Htmx is used at our company mainly to monitor and list some internal resources and their usage. Almost every developer uses it everyday and no one knows its htmx. Im probably going to add a footer like "Made with HTMX"

@HAMYLABS 3 ай бұрын

I have a feeling this is true at a lot of places. People quietly start using it for internal dashboards or small parts of a page. But it's not shared widely so broader org and ppl like me don't see it. Then eventually people are like oh we're already using this for small things, let's try it for a big thing. I think that's HTMX's silent superpower - it's easy to adopt in experiments so may quietly start getting integrated into core products.

@StingSting844 3 ай бұрын

@@HAMYLABS i believe it's not ready for full products yet because a lot of modern apps have a lot of complex interactions that are simply going to look slower with htmx. I see this after developing some pages with it and I had to use web components wherever I needed the operations to be fast on the client side.

@C4CH3S 3 ай бұрын

@@StingSting844I definitely see a need for a framework that combines hypermedia controls and reactivity. Sometimes you simply need to break the rules of REST and have the client do the work. Svelte is really close, sadly it doesn't play well when you want to serve it from a real backend language instead of node. It's hard to serve these as MVC/MVU server rendered pages because you have to follow their way of handling state and passing it to the "Views"

@dovh49 3 ай бұрын

I build an offline first PWA with an HTMX-like library that I built myself. Works great, even the highly dynamic pages that might have been better built with a lightweight SPA framework like Vanjs.

@alexkelly757 3 ай бұрын

CaErsons hypermedia book is a joy to read.

@HAMYLABS 3 ай бұрын

Hypermedia Systems is great! You can read the full thing online for free at his website - hypermedia.systems/

@DriftlessCryptoToo 3 ай бұрын

Bravo! HTMX ROCKS!

@AlexEscalante 24 күн бұрын

About jobs: I find hard to believe that anyone is going to get a job just for knowing how to use HTMX

@HAMYLABS 23 күн бұрын

Yeah ideally ppl aren't hired just for knowing a particular technology as theoretically they should be able to learn most technologies if they have a decent foundation but still ppl do hire based on experience w React, Knockout, Vue, Angular, etc.

@AlexEscalante 23 күн бұрын

@@HAMYLABS Well, React makes a lot more sense since it's a whole ecosystem.

@dandogamer 3 ай бұрын

Im using HTMX on a production site alongside Astro and i must say i dont enjoy it. You lose all the benefits of scoped styles and JS when you attempt to navigate to a page via HTMX as it doesnt know how to load the css. So youre forced to either create a global css file (which i did) or resort to something like tailwind. Also the export const partial = true. Doesnt even work and leads to some nested components not even rendering. Very poor integration by astro. But in terms of pure HTMX i still dislike how everything becomes magic IDs

@HAMYLABS 3 ай бұрын

Yeah with HTMX you lose some of the magic of SPAs / JS frameworks. That can be both a pro and con depending on perspective.

@dovh49 3 ай бұрын

I've used an HTMX-like lib and am able to have custom CSS per page. It's really not too hard to do. But, yes, you have to set it up yourself, whatever pattern you use to do it. Also, it's not too difficult to have JS per page. Just put everything in a web components and if you use it you need to add the JS to that page. It's hard to describe here on youtube comments. But it is possible and not too difficult. You just have to think differently. I imagine if you worked with someone that already knows the in and outs of using HTMX then you would find it easy and easier than JS frameworks.

@depafrom5277 3 ай бұрын

Good luck building rich modern UX with HTMX, myself and many others have been burnt by it. For very trivial UI HTMX is probably fine, but even for that you are creating a mess on your backend, spaghetti of scattered HTML snippets, inbound & outbound events, gymnastics to get basic 3rd party packages bound to the rendered HTMX - not for me!

@raptorate2872 3 ай бұрын

. . . . . . You are joking right ? HTMX can be used along with any UI component library or hell with whatever flavour of CSS you want. Are you guys new to programming or only know JS web dev ? You only need one either go/python/beam for any backend needs and can scale at large. Modern web devs who lean too much on frameworks are the main problem in the industry as they lack deep knowledge on computers and programming.

@depafrom5277 3 ай бұрын

@@raptorate2872 I'm not joking. We've been using HTMX for about 2 years now and still use it on a daily basis. HTMX was adopted by some of the senior backend engineers back then and I they mostly insist we use it. I am a full stack dev with many years experience in different paradigms, and I'm not going to try convince you of the serious shortcomings of HTMX when it comes to professional modern UX. If you have not run into these problems yet then you either have very trivial UI use-cases or you just despise frontend technologies. HTMX has been on the hype train for a long time, yet it has not taken away market share from serious frontend tech like Nextjs, Remix, Svelte, Vite etc. purely because it cannot deliver the same result on the frontend, and creates a dirty fragmented mess on the backend - the benchmark for UI/UX these days is very high, better use the right tools for the job.

@axMf3qTI 3 ай бұрын

Please show your rich modern UX that can't be build with HTMX. I'm really curious where all those rich modern UX builds I keep hearing about can be found on the web.

@nd_otd 3 ай бұрын

Why are you scattering HTML snippets all around the codebase instead of just templating them in one location and just feeding data to it? It seems more like a codebase organization/standardization issue to me.

@edmundob.guevarra9565 3 ай бұрын

you sound like some noob millennial coder who only learnt JS and React