https://htmx.org logo
Join Discord
Powered by
# htmx-general
  • g
    When they have to look outside React (or insert many other frameworks here), they're so scared, they pee a little and then scream against the idea they even have to consider letting go of React
  • g
    Basically, they're Gollum and React (or other frameworks) are their ring
  • g
  • m
    it is difficult to get a man to understand something, when his salary depends upon his not understanding it
  • g
    i saved this quote 😂 built using htmx btw

    https://cdn.discordapp.com/attachments/725789747212976259/1105232703206469712/Screen_Shot_2023-05-08_at_16.39.38.pngâ–¾

  • b
    no idea how anyone makes sense of react
  • b
    just looks like a whole load of hoops to jump through
  • b
    the only "framework" i like is svelte
  • b
    in quotes because its not actually a framework obviously
  • m
  • m
    \> infinitely faster i have to admit this is one area where I just don't have enough experience (w/ vue, react, etc.) since I built intercooler.js and just stayed w/ that. People ask me to compare htmx w/ those frameworks or start saying stuff like "well, how do you transpile the server side hydration into your reactive core without the hooks blowing up?" and I'm like...
  • m
    i feel like I should really build a react app at some point just so I know wth i'm even talking about when comparing them
  • g
    i tried to build a todomvc in react once
  • g
    i did everything the obvious way and for some reason it had multi-second lag spikes
  • m
    this is one reason why I really value the feedback of folks like @great-article-50141 and @melodic-advantage-28381 who have walked the walk
  • g
    i deal with React in production sometimes, and the problem is almost always someone forgot to add a hook dependency in the array...
  • m
    help me understand this
  • m
    my understanding is that react reacts to data changes
  • m
    so what are hooks?
  • m
    the sound like events/callbacks
  • m
    but that doesn't sound very reactive to me
  • g
    it's a callback for a lifecycle change (component was loaded for the first time, component was rendered, etc.)
  • m
    and what sort of code do you write in these hooks?
  • g
    you can e.g. make network requests, change the internal state of the component, anything which is not purely 'render HTML'. with hooks they were trying to compartmentalize these impure parts inside callbacks so they wouldn't interfere with the main render loop
  • m
    mmm
  • b
  • b
    this has a fairly simple example
  • b
    basically you have a state or set of states that can be changed and the component will react to the change "on it's own"
  • g
    React is like a mini runtime for pure HTML rendering + impure effects, it decides when to interleave them
  • b
    the first impression looking at hooks can be pretty awful but they actually make some sense once you work with them
1...111811191120...1146Latest