[blacktriangle]

Alpine does look neat, but it feels like its coming at the problem from a different direction than I'm thinking. Alpine looks like it wants to expose you to JS functionality via HTML attributes. My issue with this approach is that every time I've tried it, one eventually hits the limits of what the tool anticipated. Also Alpine looks like it leans on putting literal JS into HTML tags for execution which I don't like since this code is often difficult to debug, lint, reuse, etc.

I prefer the alternative approach where you move as much of the system as you can into JS, since JS is a fully functional language that will adapt to any issue you might run into. Your static HTML would really just be a static skeleton focusing on layout leaving your dynamic content to be dynamically created by JS. Your JS could keep references to those elements in code and then not rely on selectors to find what you need.

With web assembly I'd be really shocked if it was able to provide the same kind of dynamic interactive environment as the Javascript console, but I'm not that well versed in webasm so who knows?

[ducharmdev]

Definitely feel the same way about Alpine. Philosophically I get it, but I agree about how using attributes obfuscates too much. The idea of debugging js in attributes sounds horrible.

Not sure if you've used the multiline console that Firefox has, but I could easily see some repl-driven development with that; I just wish the other browsers had it too.