https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • t
    It reads to me like this person has an obscenely complicated backend for no good reason
  • m
    I read it as a front end engineer who hasn't spent much time building with hypermedia and, thus, thinks about how to do things the SPA way, but with hypermedia. Understandable. And, of course, hypermedia does have its limitations. The good news is that none of this matters.
  • m
    Dw one day the world will enter enlightenment. Just not today
  • s
    People will argue about everything, you cant satisfy everyone
  • a
    Yeah I can't relate with most of those HN comments. I've been spending the past 4 months or so going around and refreshing my knowledge on frontend offerings. There are two massive standouts: - HTMX - Svelte I'll choose svelte for my flashy projects, I'll choose HTMX for the ones I want to last forever
  • s
    whats all that svelte hype about tho
  • s
    is it a fullstack framework or just frontent?
  • o
    SolidJS and Qwik too but they're still too early/underdeveloped in places.
  • r
    Svelte "revolutionized" frontend by implementing compilation time reactivity. Instead of VDOM, that React and Vue use, Svelte introduced built-time dependency tracking, generating more efficient update logic with less overhead
  • s
    what was that message about 2mb something?
  • s
    xd
  • r
    It ALSO intoduced hacks like 
    arr = arr
    because compiler can only track explicit assignments, so if you used mutating array functions or updated specific object fields - tough luck
  • o
    I said what @ripe-action-67367 sent above but in a cynical way
  • s
    ohh thats interesting. I saw fireship io use it a lot
  • a
    I have a need to use hx-target on something without an ID, and it is on a separate part of the page, so I haven't been able to get "closest" or "find" to work on a CSS selector. Is there another way to target perhaps by name or a class?
  • o
  • m
    i don't agree!
  • m
    is it possible to add an id to it (or around it) so a CSS selector can be created?
  • h
    @mysterious-toddler-20573 I think I've found a memory leak. I've been trying to track down why detached nodes increase significantly over time, when swapping. The obvious cause would be references to nodes that can't be garbage collected. I think the variable 
    body
    here is the culprit, as you're using it inside a timeout: https://github.com/bigskysoftware/htmx/blob/560b3140740f4be386acd044af7568ed7ae19557/src/htmx.js#L3403 Changing as follows seems to stop detached dom nodes accumulating:
    Copy code
    js
setTimeout(function () {
   triggerEvent(body, 'htmx:load', {}); // give ready handlers a chance to load up before firing this event
   body = null; // kill reference for gc
}, 0);
    Can anyone else verify this? You can test your project by looking at how the graph of dom nodes varies over time in Chrome's performance monitor tool.
  • m
    I would expect a memory leak to be up and to the right
  • m
    did you do a page refresh at the top?
  • m
    that setTimeout doesn't appear to have any particular nodes in context
  • m
    otoh, this is javascript
  • h
    That’s a screenshot with my fix. Previously the node count only went upwards.
  • h
    No refresh
  • h
    Would be good to know if that is a general finding or specific to my projects.
  • m
    ahh
  • m
    boy, I can't see how that would capture and hang on to stuff
  • m
    https://grugbrain.dev/#grug-on-closures > javascript developers call very special complexity demon spirit in javascript "callback hell" because too much closure used by javascript libraries very sad but also javascript developer get what deserved let grug be frank
  • h
    I’ve come across the 
    setTimeout()
    problem a few times before. It’s usually best to created references to dom nodes inside the function, rather than reuse an existing one, because the garbage collector will refuse to mark it for collection.
1...106810691070...1146Latest