First, thanks for checking it out! It is a different way of coding for sure, so I think a walkthrough comparison would be a good thing, especially for web components, as you suggest. What I’ll do is set up a page on the website that compares the two approaches step by step, something like that.
I will say here though, the main DX improvement though is the intuitivity of coding. I’ll do a comparison with CSS.
With CSS, you don’t have to think particularly to assign a style - you just write it, you know? CSS is very quick and intuitive once you know your selectors, commands and the hierachical rules. CSS is generally pleasant to code in. Fun even!
CSS makes things a lot quicker. CSS wins every time - no argument. No one is out there trying to reinvent CSS.
Currently, we have a similar situation with DOM manipulation. Anything too complex is left to the plugin or framework developers, and best practices become “use a framework” and “don’t reinvent the wheel”. Right now, you’d need some sort of recent CS degree to keep up with progress in UI frameworks. We have the same symptoms in the community that would exist for styling if CSS did not exist.
For what? Adding and removing elements? Changing styles and properties? Updating content in an element? It shouldn’t be rocket-science.
But all that is needed to solve it is some higher-level abstraction.
So Active CSS solves the same problem that CSS did, in exactly the same way that CSS did. It really isn’t anything new - it is just an extension of CSS.
So in practice, that is probably the most notable DX improvement.