4 ms·

There is the occasional tech talk on YouTube where some kind of migration from React to HTMX in a large project is discussed. You will have to search though as

There is the occasional tech talk on YouTube where some kind of migration from React to HTMX in a large project is discussed. You will have to search though as I do not have any links at the ready. However I have not seen anything really substantial either that confirms that HTMX works in large projects just as well as in smaller ones. I plan to use HTMX in another larger, upcoming project though as I want to gain some insights on the side too. That being said I am aware that it might turn out to be a mess. But I would be content with the fact that HTMX is generally very useful for smaller projects and just put it in my respective imaginary toolbox to keep in mind for those kinds of projects.

rob 3y ago
Link, from 2022: https://htmx.org/essays/a-real-world-react-to-htmx-port/ https://htmx.org/essays/a-real-world-react-to-htmx-port/ Every time this is brought up (use in larger projects), people usually only mention this article/video and nothing else, so I'm not sure if that's a good or bad thing.
- karmarepellent 3y ago
  Yes, that is exactly my point! I think the lack of real world examples of large HTMX projects is a little telling. But it might just be large projects usually happen in large companies where you aren't necessarily allowed to disclose project details to the community. Again, I think at this stage the best way to determine if HTMX is a viable option for large projects is to try and ideally share your insights. To be honest I am looking forward to the day when we can put all the HTMX/React whatever debates to rest and it will just be another great tool amongst other tools.
  - Woshiwuja 3y ago
    to be fair unless you are doing a complete rewrite it doenst make much sense to swap frontend. I bet we will see later this year htmx getting used because of people getting confortable with it
    - cqqxo4zV46cp 3y ago
      htmx’s growth trajectory isn’t as steep as you’re making out with that expectation. I remember seeing conference talks about it ages ago. It’s ostensibly getting more interest now sure, if not legitimate adoption, but it does feel like more of the early starters would have something to share by now. For the record, I hope that it succeeds.
      - recursivedoubts 3y ago
        finished a close second behind react and ahead of svelte, vue, vue2, vue + vue2, angular, solidjs, quick: https://star-history.com/#bigskysoftware/htmx&bigskysoftware/_hyperscript&Date https://star-history.com/#bigskysoftware/htmx&bigskysoftware... idk what a steep growth trajectory is to you, but this has felt pretty steep to me: https://star-history.com/#bigskysoftware/htmx&bigskysoftware/_hyperscript&Date https://star-history.com/#bigskysoftware/htmx&bigskysoftware...
        Woshiwuja 3y ago
        also: https://star-history.com/#bigskysoftware/htmx&facebook/react&Date https://star-history.com/#bigskysoftware/htmx&facebook/react...
        recursivedoubts 3y ago
        sure, but click "align timelines" and then consider I'm a one man shop in montana, and facebook is, well, facebook: https://star-history.com/#bigskysoftware/htmx&facebook/react&Timeline https://star-history.com/#bigskysoftware/htmx&facebook/react... not saying htmx is gonna replace react any time soon, but c'mon, it finished #2 right behind react in rising stars, that's pretty good
        Woshiwuja 3y ago
        Its awesome, makes you wanna write actual webapps instead of using the backend just for db queries
- boringuser2 3y ago
  >The effort took about 2 months (with a 21K LOC code base, mostly JavaScript) That isn't a very large codebase for frontend, I'd expect one person to be able to do that in less than one month if they're actually trying.
zer00eyz 3y ago
>> that confirms that HTMX works in large projects Define large? By size of project or volume of users. HTMX is more targeted for the latter, not the former. THere is a continuum. Static pages, SSG's on one side, and SPAs/react all the way at the opposite end. They both do VERY different things. HTMX is some where in the middle, think content heavy PAGES that need lightweight public facing interaction (email/contact, validation loops, a form or two, maybe some dynamic conversions, a carrousel) Static home page for cache performance, html for sales contact cycle, react for the app you sell ... all three can and should be coexisting!

rob 3y ago

Link, from 2022: https://htmx.org/essays/a-real-world-react-to-htmx-port/ https://htmx.org/essays/a-real-world-react-to-htmx-port/ Every time this is brought up (use in larger projects), people usually only mention this article/video and nothing else, so I'm not sure if that's a good or bad thing.

karmarepellent 3y ago
Yes, that is exactly my point! I think the lack of real world examples of large HTMX projects is a little telling. But it might just be large projects usually happen in large companies where you aren't necessarily allowed to disclose project details to the community. Again, I think at this stage the best way to determine if HTMX is a viable option for large projects is to try and ideally share your insights. To be honest I am looking forward to the day when we can put all the HTMX/React whatever debates to rest and it will just be another great tool amongst other tools.
- Woshiwuja 3y ago
  to be fair unless you are doing a complete rewrite it doenst make much sense to swap frontend. I bet we will see later this year htmx getting used because of people getting confortable with it
  - cqqxo4zV46cp 3y ago
    htmx’s growth trajectory isn’t as steep as you’re making out with that expectation. I remember seeing conference talks about it ages ago. It’s ostensibly getting more interest now sure, if not legitimate adoption, but it does feel like more of the early starters would have something to share by now. For the record, I hope that it succeeds.
    - recursivedoubts 3y ago
      finished a close second behind react and ahead of svelte, vue, vue2, vue + vue2, angular, solidjs, quick: https://star-history.com/#bigskysoftware/htmx&bigskysoftware/_hyperscript&Date https://star-history.com/#bigskysoftware/htmx&bigskysoftware... idk what a steep growth trajectory is to you, but this has felt pretty steep to me: https://star-history.com/#bigskysoftware/htmx&bigskysoftware/_hyperscript&Date https://star-history.com/#bigskysoftware/htmx&bigskysoftware...
      - Woshiwuja 3y ago
        also: https://star-history.com/#bigskysoftware/htmx&facebook/react&Date https://star-history.com/#bigskysoftware/htmx&facebook/react...
        recursivedoubts 3y ago
        sure, but click "align timelines" and then consider I'm a one man shop in montana, and facebook is, well, facebook: https://star-history.com/#bigskysoftware/htmx&facebook/react&Timeline https://star-history.com/#bigskysoftware/htmx&facebook/react... not saying htmx is gonna replace react any time soon, but c'mon, it finished #2 right behind react in rising stars, that's pretty good
        Woshiwuja 3y ago
        Its awesome, makes you wanna write actual webapps instead of using the backend just for db queries
boringuser2 3y ago
>The effort took about 2 months (with a 21K LOC code base, mostly JavaScript) That isn't a very large codebase for frontend, I'd expect one person to be able to do that in less than one month if they're actually trying.

zer00eyz 3y ago

>> that confirms that HTMX works in large projects Define large? By size of project or volume of users. HTMX is more targeted for the latter, not the former. THere is a continuum. Static pages, SSG's on one side, and SPAs/react all the way at the opposite end. They both do VERY different things. HTMX is some where in the middle, think content heavy PAGES that need lightweight public facing interaction (email/contact, validation loops, a form or two, maybe some dynamic conversions, a carrousel) Static home page for cache performance, html for sales contact cycle, react for the app you sell ... all three can and should be coexisting!