I used to read the comments rather than the articles on HN because they were once so insightful but these days... just wow. I don't think I'm more knowledgeable, smarter, more talented or more able than anyone (to be honest I'm pretty dumb) but something has definitely changed for the worse.

i mean some of these comments are almost verbatim: "I don't know anything about htmx but it's obviously terrible"

i mean straight up admitting they don't know anything about the subject material and then making stupid claims

I wouldn't be here if I dismissed anything as easily as most of the commenters over there. I wonder if concrete examples would maybe at least get them to look at htmx more seriously. Something like the instagram clone in htmx vs svelte or other modern monstrosities.

I've been working on an MVP for something and I've definitely been hitting some weird cases with htmx. I had to do a hack where I redirect a user to load a small html chunk in order to populate the URL (it was originally form a form input). If I refresh the page, it only loads the small piece of htmx chunk in the browser since that is all that was returned. There might be some pattern I'm not aware of to do url management so that refresh, history, and link sharing work properly. The other thing is that it's enabled me to be really productive as one person. However I am nervous that as I add another couple of devs, it may get less tenable

@User check the docs for url management. deep linking and refreshing should work, fully supported.

one thing that htmx doesn't do is implement any abstractions around concepts that would make it much easier to work with larger teams. That's up to you and the backend framework you use. Django HTMX (probably) has existing patterns that would simplify use and reuse of htmx techniques.

OH, maybe I need a HX-Refresh header

so the whole page gets refreshed 😄

can't say without knowing in full detail your usecase, but between that and https://htmx.org/docs/#history you should be able to implement a correct solution without hacks

There are definitely some approaches like componentizing reusable widgets to be embedded with different context in different areas that I've started to realize when I was using the same item in multiple places

Django htmx you are referring to here, is this a particular package or the channel in this discord

i don't know if it's a package more than a "stack" but there's a lot of literature out there (and a few libraries for integration tools)

I stopped reading hackernews comments a long time ago, these days the only use I have left for hackernews is as a community curated source of tech news that might be interesting .

One thing that has made it easy to get started for real for something like next.js is this repo https://github.com/gothinkster/realworld

if someone made a django + htmx or + htmx that implemented the real world demo spec I think it would be killer for htmx

I would be down to help here and there (mostly would be learning for me) -- would need someone who is an expert to scaffold "the right way" to organize things

not sure what you're asking for

there's plenty of django+htmx demos out there

yeah, and they've been pretty helpful. The link above is a specification or standard and widely referenced demo app that I know many people use to understand how a new framework is supposed to be used idiomatically for non-trivial use cases

the idioms are still being discovered and formed

👍 it will be a milestone for adoption is to 1) discover the idioms, 2) be able to demonstrate them in a unified way. Being able to implement the specified app above would also be an ahah moment for people coming from UI frameworks to map things to being done with htmx, the dismissive hn responses are usually when someone has a mental model for something and is not able to adopt an alternate one because they need an example

haha or they are just dismissive for fun because they invested a lot of time getting their own mental model to a good place

"libraries like htmx are rather primitive compared to tools like svelte" <-- this should be a badge of honor.

agreed, maybe start a conversation in #864934037381971988 and get some fellow djangonauts to join in?

Loved this article, only thing for me that stood out was the mpa loads JavaScript libraries every request. In particular the script having to be executed everytime. So my question is should I avoid page refreshes 90% of the time? Say for ecomm site a list of products and user clicks on one for detail. Should I do a standard form submit or replace the html to avoid the reexecution of the htmx library. This question is kind semi rhetorical tbh.

Oh I like this response: > ...I want more "primitive" tools like htmx. > Light sabres, not death stars.

not sure if serious, but

hx-boost

can give you most of what you need here, and generally HTML partial replacement obviates this issue 🙂