A worthwhile experiment, absolutely, but I can’t see myself ever using this for a serious production application. I hope we keep iterating on this before settling for a non-turing complete, directive-driven language that gives Angular 1.0 PTSD flashbacks
I've spent a few days playing around with #HTMX, and I'd like some insights from people who are using it in production. Doesn't need to be a paid project, but more than just "my pet experiment".
What are you using it for?
Like, to me it feels as if either the backend needs to be really tailored to HTMX, with HTML fragments and custom headers and stuff, or you need to start writing non-trivial amounts of JS in the frontend for anything but the most basic tasks.
Every few months, I come back to rewriting a #todo app in #aspnetcore, sometimes it's with Blazor, sometimes it's Razor Pages, and this time with #Htmx (although I may have already done HTMX 😅)
I got some quality-of-life improvement issues entered to help make #JetBrainsRider better, too. So that's a win!
If there was an #HTML element that changes it's content when users interact with other elements on the page, what name would it have?
PLEASE NOTE: I am not suggesting that this element needs to exist; I am only asking what it would be called. I'm building a CustomElement, I just want it to have a name that makes sense.
Vote and suggest others in replies. Please boost for reach!
Usssh, now I’ve done it. I actually have to talk about htmx and blazor next monday. So I need all you folks help, what are the libraries you are using? What are the good and bad things about that combo?
See attached image for the HTML from the DOM as I tried to edit a field. Never mind the lack of accName or that it replaces the row in the DOM for a different row.
Very excited about the latest feature/workflow I’m adding to Kitten. I call it… 🥁
✨ Streaming HTML ✨
Implement back-end functionality and stream HTML updates to the client without writing any front-end JavaScript.
Just give your forms names and listen for them in an onConnect() handler you export from your page. Kitten handles everything else – setting up a WebSocket route for you, mapping triggers to events, etc. – thanks to Kitten + #htmx magic 🪄
So I’m genuinely puzzled by #htmx. Do you folks who use it return html fragments? Or do you just render a whole page and extract single nodes? If you do the first, how is this “better” than just returning json and rendering it on the frontend?
I don’t really understand the architectural premise and the hypermedia systems book doesn’t really help me click.
I want to share an update of my web app project. I was working on it the last few days and chose to use only #Bootstrap, #htmx and server-side rendering with a #Golang backend.
The goal is to replicate (or replace) an existing app that is built with a heavy and very limited proprietary RAD tool.
It feels a little old school (say hello to FORM :-D), but it is SO GOOD. With htmx and traditional server-side rendering I can build anything, debug anything and it just works. I now have around 6k lines of HTML and Go code, did not write a single line of JavaScript and use no JSON. Also, I don't have to build a JSON API on the backend for every piece of data I need. SQL is my "REST API" now.
Feels very productive. I think I found joy in web development again. :')
A fifteen-second demo of how you can create a toast message in 42 lines of code¹ without writing any client-side JavaScript using Streaming HTML² in Kitten³.
#HTMX is made and used by people who take a screw and force it into a wall with a hammer, permanently asking: 'Why should only nails be used like nails?'
They are screwing things up and create a total mess. #accessibility #Barrierefreiheit
(Explanation for outsiders: HTMX wishes to be an extension to websites by changing the purpose of things that are already thought out well and behave in predictable ways. It's like taking a car and change the trunk into an engine, regardless of #usability.)
not sure who's an #htmx developer on Mastodon: maybe @benpate? https://mastodon.social/@sil/110340165942981980 thread has some useful pointers on accessibility in HTMX examples, i.e., there isn't much and there should be :) I know very little about HTMX, having only discovered it today, but this sort of thing does incline me against looking further at it, so perhaps that might be an area worth looking a bit more into, HTMX team?
Had a lot more "fun" with #HTMX today. Main problem was that I can't make a div element behave like a button inside a form. (Which I needed to refactor a JavaScript mess without changing the CSS too much)
The current solution: Writing vanilla JavaScript (see https://htmx.org/api/) - then tacking hx-on="click: myJSfunc(...)" onto the divs and doing the htmx.ajax request from my custom JS code.
I just watched @pythonbynight's #DjancoCon talk on the current state of #HTMX in #Django and now I'm turn between trying out django-render-block, forge-htmx, and @carlton's django-template-partials.
Anyone written a blog post or made a repository attempting to write the same HTMX-powered view(s) using all 3 of those packages? I'd love to compare and contrast them more directly.
So I got my Razor Pages demo working with #HTMX boost concept and view transitions. And with a few lines of CSS and no #aspnetcore backend changes, I get this sweet transition animation. What do you think, #dotnet folks?