> turing-complete piece of thinking sludge Don't let the new-born AI sentience hear this, them's fighting words. But it does illustrate the kind of power that

> turing-complete piece of thinking sludge Don't let the new-born AI sentience hear this, them's fighting words. But it does illustrate the kind of power that JavaScript gives. The language and especially its ecosystem is a jungle of abstractions and complications, hard to control and easy to break. That includes React and Next.js, speaking as someone who is still deep in that world. > put HTMX on the small computers, they can talk to the big computer and ask for bits of stuff whenever they want. And my nice big computer can do all the thinking That's a nice way to describe it. HTMX is re-thinking the problem space from the ground up, starting with HTML. That's a lot simpler to reason about, directly working with the user interface as it is rendered in the browser. How that HTML is dynamically generated is left up to the server, the actual "thinking" part. > "type script"? Ah yes just what a language..made out of warm toffee needs, homotopy type theory TypeScript is brilliant though, it's the best thing that could have happened to JavaScript. For what it had to work with as a starting point, it builds on that foundation a language that's more sane and reliable. With a type system that's at least better than before - implicit/invisible types or none at all. And the language server that enables intellisense, it's an ingenious way to empower the code editor - I use it heavily and can't imagine programming without it now. > make your server-side endpoints either return the full template or a partial component depending on the whether the HX-Request HTTP header is present Good to know! I'm still learning how to use HTMX, especially on the server side. It's a different way of thinking than an API with JSON.