That's a fantastic idea! I've made it a bit simpler for myself — basically just `source file`, so that I don't need to press enter to execute it, but also added one cute detail in the loop:
if [[ -f "$target/.exec" ]]; then
zsh "$target/.exec"
fi
Actions are somewhat similar, yeah, even if much more limited.
Svelte was too js-heavy, and it requires js backend to be rendered on the server - while we had no js engineers. Plus markup was already done, as we rendered it server-side when using React.
There is no way to render JSON as HTML right now, it expects server to return HTML.
OTOH that's an interesting thought and it feels like just an addition of one command to whatever there are in actions ( https://twinspark.js.org/api/ts-action/ ) right now... I need to think about it a bit. :)
It's more like an alternative implementation of htmx. Alpine is more about "let's do components in HTML", and this one is more of an idea "how do not go there, but still have practical results". :)
Two reasons really: I wrote it before htmx appeared, so it already existed and a few projects were using it in production. And second one - I really hate attribute inheritance, and it’s everywhere in htmx…
I haven't read your report completely, but it's very interesting.
I would love to hear a bit more details about query selector performance. Could you maybe provide some details or a pointer where this was tested?
Also about websockets vs HTTP calls: HTTP calls do not open separate socket connection even when you're using HTTP/1.1 with keep alive, with HTTP/2 it's a default way of working, so should not be a problem. I guess something else is a culprit here?
It's not even close - it's not feasible to develop a real server application in a notebook, while you're absolutely will be doing REPL-driven development in Clojure.
This is probably the worst use of the word "shortened" ever, and it should be more like "mutilated"?