[HN Gopher] Htmx 1.9.0 has been released
       ___________________________________________________________________
        
       Htmx 1.9.0 has been released
        
       Author : vyrotek
       Score  : 150 points
       Date   : 2023-04-11 19:35 UTC (3 hours ago)
        
 (HTM) web link (htmx.org)
 (TXT) w3m dump (htmx.org)
        
       | sdze wrote:
       | Fantastic update. Also, I can't wait for Hyperscript to get to
       | its maturity (1.0). ;)
        
       | ye-olde-sysrq wrote:
       | I know this is tangential but I was trying to decide what I
       | wanted to use to make an app that could be accessed from android,
       | ios, and desktop in a convenient way. I am not a fan of how
       | churny the js world is, and I come from a background in
       | Swing/Qt/GTK/etc desktop development.
       | 
       | I evaluated HTMX as a not-js way to do modern web apps. It was
       | fine, it was certainly interesting. I had some concern about how
       | much pain I would be in for when I inevitably wanted to borrow
       | something from the js ecosystem, like a charting library or
       | something.
       | 
       | I actually ended up deciding on godot with gdscript and while I'm
       | not done yet, I'm having a pretty dang good time. I'm a little
       | annoyed that I have to pay apple to get it on iOS, but I have to
       | pay apple anyway because safari is such an annoying odd one out
       | from how firefox and chrome's renderers work. It's always safari
       | that has weird things it doesn't like, in my experience. And I
       | have hope that either Epic Games or Europe will manage to force
       | Apple to let people sideload apps.
        
         | Takennickname wrote:
         | Doesn't godot refresh the entire screen at X fps? That would
         | kill battery life, no? Asking cuz I considered this route
         | before but decided against it for battery and app loading time
         | reasons.
        
           | DisownedWheat wrote:
           | Godot does have a low CPU mode that limits screen refreshes
           | until something is interacted with on screen or animated,
           | it's what the actual editor uses. I'm not sure whether it
           | works on web exports though.
        
           | boterock wrote:
           | godot ticks at that rate, but if you don't transform UI
           | things, they don't get redrawn. so maybe the framebuffer is
           | switched every frame, but draw calls shouldn't be reissued
           | unless needed.
           | 
           | also, I think it is possible to make it not tick from time
           | updates, but only from input event updates, or maybe an
           | animation actually running. similar to what the editor does.
        
         | somethoughts wrote:
         | From what I could tell the sweet spot for HTMX would be much
         | more targeted at adding some JS magic to an existing backend
         | server based web app (i.e. Django, Flask, Rails) where the
         | developer primarily is a Python/Ruby, HTML/DOM and database
         | expert and doesn't want to get bogged down into supporting a
         | full fledged frontend like React, Angular, etc. to add some UX
         | flair to their mostly CRUD based app.
         | 
         | Native apps (i.e. iOS, Android, MacOS) purely in HTMX is
         | probably not its sweet spot. Probably Electron (or Godot) would
         | be better.
        
           | recursivedoubts wrote:
           | there is a really neat mobile-native hypermedia called
           | HyperView:
           | 
           | https://hyperview.org/
           | 
           | which is discussed in depth in our book:
           | 
           | https://hypermedia.systems/book/hyperview-a-mobile-
           | hypermedi...
        
         | PaulHoule wrote:
         | I am using d3.js inside an htmx app with no problems.
        
       | jonathan-adly wrote:
       | If you are on the fence about using htmx in production. my
       | startup[0] uses it exclusively for our frontend (with like 2
       | lines of hyperscript. It's sister library). No complaints and
       | boy, it's such a fresh breath of increased productivity and still
       | excellent user experience.
       | 
       | We still had to build an API anyway for external organizations
       | using our product, but you still skip a ton of unnecessary JS
       | code.
       | 
       | 0. GalenAI.co
        
         | powersnail wrote:
         | What's the back-end? Do you generate those HTML responses via a
         | normal template engine, or is there some sort of deeper
         | integration with HTMX on the backend?
        
       | schemescape wrote:
       | Anyone planning to make a browser with native support for HTMX
       | (instead of a full JavaScript runtime)?
       | 
       | I only ask because I kind of wish such a thing existed.
       | 
       | I still can't find a happy medium between no JS and "browser as
       | an entire OS".
        
         | recursivedoubts wrote:
         | my hope is that, at some point, the browser developers notice
         | htmx and decide to fold its functionality into HTML itself,
         | which is where most of this stuff belongs
        
       | seumars wrote:
       | What's the consensus on using custom HTML attributes such as "hx-
       | post", "hx-trigger" and so on, which are "invalid" according to
       | the spec? I don't mind prepending data- to custom attributes but
       | it's still a minor nuisance.
        
       | benatkin wrote:
       | Does it play nicely with custom elements and the shadow DOM?
        
         | recursivedoubts wrote:
         | as far as I understand, it does a visual snapshot of the DOM,
         | so it should work w/ custom elements just fine
        
           | canadianfella wrote:
           | [dead]
        
         | djbusby wrote:
         | I'm using a combination of RiotJS and HTMX. But RiotJS isn't
         | exactly shadow DOM.
        
       | JoshWVS wrote:
       | Woah--I stumbled upon "Hypermedia Systems"[0] from the View
       | Transitions essay linked on this release page. If, like me,
       | you're sympathetic to the htmx philosophy, but not really an
       | expert, it looks like a great read. (And it's beautifully
       | presented, too.)
       | 
       | Seems it was discussed a few months ago[1]; I missed it then.
       | 
       | [0]: https://hypermedia.systems/
       | 
       | [1]: https://news.ycombinator.com/item?id=34134545
        
       | recursivedoubts wrote:
       | this will probably get nuked since it's just a point release (no
       | hard feelings dang), but there is an interesting new feature: it
       | now has View Transitions support, an experimental browser feature
       | available in Chrome 111+ that makes visual transitions between
       | DOM states much easier to animate.
       | 
       | I discuss it in an essay here:
       | 
       | https://htmx.org/essays/view-transitions/
       | 
       | Chrome's docs on the feature are here:
       | 
       | https://developer.chrome.com/docs/web-platform/view-transiti...
       | 
       | MDN:
       | 
       | https://developer.mozilla.org/en-US/docs/Web/API/View_Transi...
       | 
       | will be exciting to see this feature rolled out across the major
       | browsers, as it will make vanilla HTML a lot smoother.
        
         | clairity wrote:
         | neat stuff!
         | 
         | you have a typo on that page under
         | https://htmx.org/essays/view-transitions/#the-css : @keframes
         | instead of @keyframes
        
           | recursivedoubts wrote:
           | thx, fixed!
        
       | durpkingOP wrote:
       | Where might I find a red cap that says "Make apps HTML again"?
        
         | [deleted]
        
       | squidsoup wrote:
       | Htmx has such an old man yells at cloud vibe. People don't like
       | fat js clients because of "view transitions", they like the
       | developer experience, composability of components, and
       | benefitting from a vibrant ecosystem that is constantly
       | innovating.
        
       ___________________________________________________________________
       (page generated 2023-04-11 23:00 UTC)