> The cultural chasm between JS developers and people who push for simplicity was huge
Yet another cheap shot. Might as well say 'fu js devs'. How come every time we have a thread on this thing its devs and supporters always come across as arrogant, bitter folks with an axe to grind.
I don't like your technology. I didn't like it several years ago when I was introduced to it, and I don't like it now. It's not a bad idea but calling me an idiot for not doing UI on the backend is not going to win over anyone that doesn't already hate js and the people who write js.
Absolutely this- Saying that the complexity of modern web dev is needless without even addressing things like state management, URL routing, component encapsulation, stylesheet encapsulation, performance, compatibility, semantic markup, offline-first, server-side rendering (for SEO and first paint) are somehow not real problems that need to be addressed. If you don't do it in the frontend, guess what? All of that is happening in the backend, too.
People seem to act like those problems just "go away" when you don't do SPA but it doesnt.
Half of those things you list are already handled by the browser, that's why htmx is so simple. Htmx does not preclude building an SPA, because all resources can be directed through service workers, but that's outside of the scope of htmx specifically. It just directs you to use hypermedia and exploit native browser technologies instead of inventing ad-hoc JS libraries and/or protocols.
Yet another cheap shot. Might as well say 'fu js devs'. How come every time we have a thread on this thing its devs and supporters always come across as arrogant, bitter folks with an axe to grind.
I don't like your technology. I didn't like it several years ago when I was introduced to it, and I don't like it now. It's not a bad idea but calling me an idiot for not doing UI on the backend is not going to win over anyone that doesn't already hate js and the people who write js.