What the hell is HTMX? 

Thanks nerd!

We have adopted htmx a couple of months ago and can confirm that our productivity skyrocketed. I totally agree with your statement "The client should be dumb". "Modern" frontend frameworks add so much complexity that it hurts. The first time you tell people what a browser is actually capable of *besides* JS is always mindblowing.

Nice video, dude! Hyped about htmx. Would love to see more on it ;)

I gotta give HTMX a try. I never realized how much time I wasted doing conditionals in my React code

This is the best explanation of htmx I have seen, and in under 4 minutes! well done

Less things to learn on client side and able to try new languages in the backend. Its a win.

The funny part is that in order to enhance and achieve the "get back to the roots"-ish behaviour and methods to use html we used JavaScript to build a little library which helps building simple reactive frontends with backends spitting out raw html as it used to back in the day As soon as the complexity of the frontend increases we would still need to get back to writing JavaScript in order to granularly adapt results to the frontend

Wow! This is the greatest video introduction of what htmx is, it's clear, concise, straight to the point and very fun to watch! referring to your video lol, not htmx :)

This sounds like kids discovering flare jeans 😉😂 but I’m all happy we’ve finally reached this stage 👍🏻 SPAs are all great for their specific functional niches but world would be a much happier place if server-heavy websites and especially internal-use CRUD apps were built using SSR. Not everything needs to be Figma 😉

After having my first JS written in 98' I'm so tired of continuous flow of frameworks, but this one looks a pretty new paradigm. Will need to check out ... (or maybe I still stick to plain HTML5, as there is no silver bullet)

Oooo, I’m ready to start exploring this new tool. Thanks for the great explanation!

Awesome, I love Htmx, the createor of Htmx is a genius 🤩😍

algorithm blessed me with your channel. subscribed. love the quick, to-the-point pace. no more 20 minute videos. thanks nerd!

I really like the way you explain stuff :)) Great vid

I have given up on JavaScript and have switched fully to HTMX. Its so much easier and overall better.

Whew you got me PUMPED on it. Hard agree. The client should be UI interactivity only. In my day job I found myself replicating similar principles in a microcosm of our React framework. We went from sending one large chunk of data to the front and having a heavy front-end to many smaller requests based upon user interactivity. Guess which one was snappier! The idea that we can offload all that data handling to the client is a falsehood when you still need data from the back-end anyways.

This video is based on the ebook found here: hypermedia.systems

First of all, avoid the opinions of most JS programmers. Anyone who is not sarcastic will be fundamentally skeptical. They will talk about how HTMX handles JSON, they will say that it is not secure. They will even cite PHP to illustrate that you are using a new templating system. Forget the haters. The thing works, and serves the purpose. The learning curve is small and, unlike other models such as Angular, Vue and React, it requires project planning with another level of maturity. Just as today, immature programmers make fun of PHP (which brought home the bacon for many developers and therefore deserves its place of respect), in the near future JS will be treated like mullets and fanny packs.

so you basically tell that with htmx now backend developer should know how to design html web pages with paddings, margins, flexboxes and so on?

after a long time in more than a decade with the mess of react, angulat, vu...... etc... , this HTMLX seems logical

when u using htmx u will get a lot of requests from client to server and those request can atchive that easy by javascript, problem is if u have alot of traffic that will do problem is servuer from requests i guess

btw how htmx can help with GraphQL or OData apis ? and what about UI libraries? Backend developers should send us fullblown components to swap?

This is definitely the future

For someone who has very little experience with html/css and javascript, what would you recommend learning, if I'm only interested in learning one framework, svelte or htmx? I'm actually a data scientist and mostly use python, but would like to learn one good framework, but only one. Thanks :3

Htmx is the future and the past rolled into one

3:20 i have been saying this for so long!

I like the fireship style of delivery😂

Looking at this now, I wonder about two things: a) why did it take decades to realize, how all this JS BS can be thrown out of web development again and b) when will these attributes get standardized, so that browsers implement them natively and we even get rid of the last bit JS to make this work?

I hope that there will come a time when people can escape the complexity of JavaScript and make a living using this language.

Awesome! thank you for this information.

I'm techincally a Blerd, my ninja

Good lord. I just listened to another RU-vid video on the same and damn near stabbed myself in the eye. I won't say which one, but this is fantastic. Thank you.

I’m wondering how fragments of ui split across front and backend is going to make things easier. Global mutable state causes challenges. Global split mutable state seems even harder. At least with json and apis the two were independent. An api that returns ui coupled to a frontend seems to add more tight coupling. At least conceptually.

Looks amazing, guess i'm fullstack now

very nice and clean explanation!

Yeaaa now implementing my backend projects in web will be much easier

I don't think anyone is going to use this directly, but I'm excited to see how React and its derivations use this to improve over time.

I'm also excited about htmx, but not creative enough for coming up with content I could show on a website. :P There is already everything made. :P

Makes thinking of the famous "The Thirty-Million Line Problem" so much bloat and layer these days even in the web.

I don't understand the example you gave. Based on the example, the frontend would make a request to "/users/1" and whatever would be returned would be based on what the backend was designed to return. The "hx-target" is just the element ID that you want to put the data that was returned in, right? How is that any different from using fetch(), getting the data, and then putting it into the HTML?

Define free, great, smart... I know JS sucks and being abused but I am truly skeptic and not ready to jump on another techwagon. Good luck guys.

This will definitely be great for making new custom web apps but that doesn’t mean don’t learn JavaScript and your frameworks since many companies or jobs cannot keep up with these new changes quickly

is also the return of Rails to prominence

Htmx cant be used for building standalone apps though, as seen with ionic. There are pros and cons with all technologies. It is important to never disregard any specific technology

Now what to do about offline ? I guess we put the logic in the service worker ? Or maybe it's just not a use case it's trying to solve ?

I love htmx; I loath modern js frameworks that adds too much overhead. Make the web simple again is great! Love htmx and alpinejs. Simple, elegant and just work!

If I have my API return HTML doesn't it mean I can no longer use this same API on my mobile/desktop app?

In terms of separation of concerns this is going a step back by coupling frontend and bancked work. But if you are not concern about this and want a full stack approach, this is good

Great video! htmx is awesome!

HTMX is great but falls short for some tasks. For exampe if I want to hide and show a part of my website. It is overhead to male a roundtrip to the server and load the whole part again and again for each toggle.

Well explained

3:28 Caching, where/howto?

Still waiting to see a live example of this

frontend should be dumb... as I'm learning React 🙄. It probably should be, but there are so many approaches to web dev it's really annoying. Like I've heard u can build sites really fast with Hugo / static site generators... this seems like apple to orange comparison tho. here's some buzzword ideas for your next videos: JSX, XML, AJAX, Wasm, websockets, vue, react when will it end???

Then in 3-years… how do we reduce the massive number of calls to the server?

i though this was fireship until i heard the voice lol

Ok, sounds like Javascipt parent child manipulation for lazy to me. We did that with a 2 GB RAM stick back then, dude!

bring back car phones!!!!!!!!!

I don’t think this is what the web needs. Can you stream data with it? Will this not open new vectors for XSS attacks?

Isn't returning html from the server coupling it was supposed to eliminate? If we decide to change the UI structure, that has to be done in the API, or am I missing something?

I've being waiting for years for js frameworks to die.

I thought that Elon musk rebranded html .....

There is absolutely no difference between the JS libraries and htmx. They all use the same dreaded JavaScript. You only write the frontend differently which i would argue that the react or the standard 'framework' setup is more modular and readable as well as easier to maintain because of good organisation. This just looks like another tailwind css library i have to learn to only get limited functionality

Daddy rambled about the good old days, skip to 2:30

golang + htmx

nice framework grandpa

how is the htmx example not equally coupled to the api response, like the js fetch example is?

why the front should be dumb and we should make everything in the back ?

Oh cool, someone has reinvented jQuery again

💞💞😍🥰🥰🥰🥰💕💕💕💕🥰🥰🥰🥰🥰🥰🥰🥰

It may be useful ony on simple frontend apps, but why use htmx on simple frontend while you can use already battle tested template engines? Can't see a point of using this.

What HTMX does it does better, but what it can't do React can. On the web the framework that does it all will always "win".

As a frontend developer, I don't like htmx. I don't see how you could create a large complex app with it.

Now if we could get PHP on the front end we would have come full circle.

nah u wrong, http obviously mean "hop to the page" lmao

you call yourself "daddy" ? what a cringe... you have watched too much of fifty shades stuff.

You've just convinced me to take HTMX seriously. Liked, subscribed. Thanks!

Very interested in learning more about HTMX. I work primarily in Rails so I wonder how it compares to Hotwire and if I should try HTMX with Rails?

PWA’s.. it was nice knowing you..

Yeh but this is basically exactly what Angular the JS was supposed to be. Also, what about the WASM? And does the DSL of HTMX limit the expression of logic in the UI? I like HTMX, especially given the it “just works” for things like SEO: no alternate static site req - which is suspect to begin with if your robots know that they’ve landed on “planet namek”