#htmx
Playing around with #flyio for hosting the #django + #wagtail + #htmx site I'm working on and I have to say, it's pretty nice to be able to do most things from the CLI. I only need the web dashboard to understand the concepts and what's going on (because I'm really dumb when it comes to hosting stuff). Nice docs and clear, honest language around costs. I really appreciate that.
Interesting... ๐ง Thoughts on HTMX making waves in the dev community? Imagine controlling dynamic HTML without heavy JavaScript. It's like ordering a 5-star meal without emptying your wallet. ๐ ๐
HTMX offers leaner, more efficient client-server communication. Think real-time updates without a page reload! For devs tired of JavaScript fatigue, this could be your new go-to. ๐๐ ๐ #WebDev #HTMX #JavaScriptRevolution
@hbuchel I'm happy we kept our focus on SSR. We use #SpringBoot #PostgreSQL and #Thymeleaf. We recently started to use #HTMX https://htmx.org The biggest challenge is having a stable&fast&integrated tool to process/bundle the JS and SCSS code where we use http://www.asset-pipeline.com
Just found out that JStachio added support for fragments specifically to support #htmx. If you are #java dev that wants to add dynamic stuff to a web front end but don't want to get into JS/TS stuff, highly recommend checking this out.
https://jstach.io/doc/jstachio/current/apidocs/#mustache_fragments
Let's gooo! #htmx merch!
https://twitter.com/htmx_org/status/1702700321800442234
Livewire seems underwhelming so far. Itโs disappointing that thereโs no thought given to #ProgressiveEnhancement. I donโt see why one would want to use that over #htmx other than theyโre used to basic bullshit like React already.
Aprendรญ tantito #htmx y es muy emocionante. Eso de la single-page-app me caรญa bien gordo tanto como usuario como desarrollador. Ora nomรกs serรก como usuario. :D
#htmx is one of those #javaScript libraries that enables all sorts of horrible #HackerNews articles like "I rebuilt my #blog using FortranScript and HTMX"
Auf geht's nach Hannover zum @JavaForumNord ๐๐#java #community #htmx #thymeleaf
Wow, #HTMX is gaining some popularity, and I AM ON THAT TRAIN.
how does htmx say i should build dynamic charts?
i was planning to use chart.js to build a custom gantt chart style thing.
but thats a slippery slope leading to more js, libraries, tooling etc.
with htmx do i just render png's? or i guess i could dynamically generate some pretty nice svg's server side ๐ค
Starting to get the hang of this #htmx thing. I'm using it to build some management pages for an internal service. Not fully convinced yet but it actually works well with #dotnet RazorPages.
Kudos to @khalidabuhakmeh for figuring a lot of this out. https://www.jetbrains.com/dotnet/guide/tutorials/htmx-aspnetcore/
New server, new #introduction:
My name isn't set yet, but I've tried Samantha and currently Melody. Online I go with m* (read m Star) and I'm from the south of Germany.
Like most people here, I am #trans (mtf), some variation of human (catgirl in my case) and highly interested in the tech sector, specifically making software do things. For this, I usually rely on #fedora as the OS with both #gnome or #kdeplasma as Environment, depending on what I feel like.
As for what funky software stuff I do: It's mostly focused on making games, utility stuff for games or utility stuff relevant for areas related to games (like a multiplatform chatbot for Twitch, YT Live, etc). For this, I mostly rely on the #godotengine and #golang. Though, I do also put my hands on #rustlang, #python, #typescript (mainly via #svelte). Other projects that I'm interested in are #htmx and #ziglang.
And some day I might also join the club of #vtubers. I even have a ref sheet already for what my character looks like. See attachment
@ArneBab Kann ich gut nachvollziehen. Wir haben nicht geziehlt konvertiert, sondern praktisch "in Typescript weitergeschrieben" und bei Gelegenheit refactored. Aber einige deiner Punkte habe ich auch so in Erinnerung.
Ich finde ja den aktuellen Hype um #htmx super. Ist zwar etwas gewรถhnungsbedรผrftig, aber man kann an Ajaxgedรถns was man so machen will wirklich alles damit formulieren. Auch per Http Header vom Server Events triggern.
The last couple of months I've been working on a little #rss reader that doubles as a (read-only) #mastodon client. The UI is closer to a Mastodon/Twitter feed than an email inbox.
I'm still experimenting with it, and it's missing a bunch of basic stuff, but I did add some cool features already, like an embedded reader mode and a send to #kindle button.
It uses #python #flask for the backend and #htmx #hyperscript #bulma for the UI.
I don't always like their videos often, but this one is gold!
I watched the quoted video when it was released, and liked it, but Prime's commentary makes it even better ๐
Shows that HTMX can be used in production! To build real things! That make money!
#htmx needs a build system so things get over complicated so people can feel they are real #software #engineers.
#webDev #html #javaScript #hypermedia #webpack #rollup #bun #vite
As much as I dig #htmx, I just can't get with #hyperscript
There's WAY too much going on in this DSL
Buried in the #HTMX docs is this neat script that lets you create a mock backend with client-side code. #JavaScript #web #development
I like #HTMX, but the guy who invented it is being an egomaniac about it on Twitter right now. https://twitter.com/htmx_org/status/1698730817370067031?s=20
Title: Hypermedia Systems
Authors: CARSON GROSS, ADAM STEPINSKI, DENฤฐZ AKลฤฐMลEK
Review: very well written and good explanation of the what/why/how of #htmx and hypermedia as it was intended. My only qualm was numerous code formatting/layout issues when ever a code block crossed pages eg missing and duplicated lines. Sometimes these lines are referred to by the text which can add to the confusion. I love the cover though and the font choices!
I'd also like a really simple "code editor" so people can write json bodies in a non-clunky way. I found this which should work out:
https://github.com/ajaxorg/ace-builds
I'm planning to try to build this with #rust and #htmx so mixing the interactivity of the editor JS + htmx sounds fun :blobfoxlaugh:
Finished my initial #hanami + #htmx slides for my upcoming talk: https://rockymtnruby.dev. Will spend the rest of the month fine tuning.
In some sense this has been several years in the making but this last year has been especially productive.
Looking forward to hanging out with folks and hopefully learn from others working in this area.
@cathodion #htmx is simple and reminds me the stacks of we use today are bloated. HTMX is learning the lessons and improving the experience and process IMO. I still have a lot to learn about it but so far I really like what I see.
> I do not like React etc., because i like LAMP
I'm a LAMP guy from way back, but I feel that Node.js fits where PHP used to just fine.
If you're writing JS on the server you might as well use the same code to render html on the backend as you do in the frontend.
React is just an HTML template engine that works in the browser too. Two birds, one stone!
But if you aren't into the Node.js ecosystem at all, then #htmx is great because there's no build, no dependencies!
I fear that a LOT of people are going to start using #HTMX for the same reason they use #TailwindCSS; it saves them from having to learn a language they don't like. #javaScript #css
Thinking about #htmx:
๐ all the #HTML gets generated on the server; the source of truth.
๐ every #DOM manipulation requires a network request.
๐ #declarative easier to reason about.
๐ app behavior declared in bespoke attribute DSL; harder to reason about.
๐ no need to duplicate #backend state on the #frontend.
๐ no offline support.
I'm amazed by the amount of stuff you can pull of with #htmx and #hyperscript. I just hacked a keyboard-friendly autocomplete/combobox without a single line of #javascript
It's super rad that #htmx supports the #ViewTransitionAPI!
This part of #htmx kinda scares me: https://htmx.org/attributes/hx-vals/#:~:text=If%20you%20use%20the%20javascript%3A%20prefix%2C%20be%20aware%20that%20you%20are%20introducing%20security%20considerations%2C%20especially%20when%20dealing%20with%20user%20input%20such%20as%20query%20strings%20or%20user%2Dgenerated%20content%2C%20which%20could%20introduce%20a%20Cross%2DSite%20Scripting%20(XSS)%20vulnerability.
hx-vals is likely a tool of last resort, like if you need to do something strange to interact with state that's external from the document.
Still, I'm not sure this is worse than if this logic were to be evaled from the console, which is always an option with any web app.
#HTMX is the future; somebody should #hireMe to build a #hypermedia #web #app for them!
Now there are some that suggest we oughtn't be shipping #DOM declaring JS to the browser at all:
#HTMX recommends returning HTML from APIs and simply rendering that according to the rules of its attributes. In other words; the only DOM manipulations that a frontend app can make are those that are handed to it by the server. The server is the only place where HTML is generated. HTMX simply hydrates it.
#HTMX is for #JS what #TailwindCSS is for #CSS
If you haven't looked at it yet, I can recommend #htmx.
A "custom" extension to html as a #JavaScript library. In a way that one might think "this should have been built in the web standard and available in browser without an additinal library".
https://htmx.org/essays/hypermedia-driven-applications/
Love it.
I'm doing some volunteer work (a custom website development using #django & #htmx). I'm out of my element, but this tech is nice enough that I can make steady progress. What I know substantially less about is hosting a Django site. Any suggestions? I need CDN, a way to update the site and run migrations and a backup service.
"And that is why HTMX is a radical concept nowadays. It is not because it's novel. Let's be clear: HTMX radicality does not surfaces from novelness. HTMX is not better than React, Vue, Svelte or any other JavaScript centered framework. HTMX is a library for the web, not a framework for JavaScript."
- Kevin Mas
This post brings to surface a paradigm shift (or back) about how web is being developed. Moving from JS centric to enhanced HTML lead by HTMX.
Kevin talks about "HTMX is filling the gap the web platform is not being able to fill.".
Which this bring us to the question of, are we in the front doors of a new approach of doing WebComponents that are HTML oriented instead of JavaScript?
#HTMX is challenging the current web development status quo, and I'm sure multiple frameworks are scared of it, and for a good reason.
They dominance are stake when we have an alternative that brings value at lower system complexity.
Motivated for what the web platform will bring to us in the next years.
I canโt believe that anyone in their same mind would bother asking why #htmx has no build step (or suggest that it should have).
I mean thatโs *exactly* why I go with HTMX over โyour favorite fancy JS frameworkโ! https://htmx.org/essays/no-build-step/