[microflash]

I've been working with webcomponents for a while. I agree that ergonomics are horrible (particularly when it comes to state management and style inheritance) but it is still better than being in a continuous churn of UI frameworks.

Unfortunately, it is the same churn that has vastly improved the ergonomics for many UI frameworks while we're stuck with the terrible workflows for authoring web components.

[dmitriid]

> but it is still better than being in a continuous churn of UI frameworks.

Is there a continuous churn?

React is 10 years this year. Vue is 9 years. Angular which feels positively ancient is 7 years (if we only count Angular 2.x).

Yes, there are newcomers like Svelte and Solid, but it's hardly a churn. Besides, they explore valuable corners that are left untouched and unexplored by other frameworks. Things like granular reactivity and removing components as a unit of UI in its entirety.

Meanwhile the "non-churn" in web components has already resulted in two deprecated standards (custom elements v0, html imports), and is rapidly churning out dozens of new standards requiring more and more javascript to paper over their egregious design (form participation, constructible stylesheets, declarative shadow dom...)

[microflash]

There's definitely a churn in the frameworks like React, Angular, Vue, etc. New APIs, breaking changes, etc are certainly a thing every year. But as always, this is both downside and upside: you get great features and valuable advances at the cost of such rapid changes.

The good news is that the tooling around the Web components is evolving even when the standard itself may moving at glacial pace.

[dmitriid]

React is compatible to its first version :)

> The good news is that the tooling around the Web components is evolving

You mean web components are growing their own frameworks at the same pace :) With new APIs and breaking changes

In 12 years web components had:

- original lib, polymer. Breaking changes 1.0-> 2.0, then completely deprecated

- lit is 4 years old, already had breaking changes in each version update 1.0->2.0->3.0 (and "potential breaking changes" even in patch releases), and adds new APIs with every release

- stencil is 5 years, has already had breaking changes in 1.0->2.0, but is probably the most stable of them all

etc.

Looks on par with the rest of the industry :)

The sad thing is that web components as a standard don't allow is for actual iteration of ideas. While Solid, S, Marko et al are exploring granular reactivity, web components are stuck in 2010. And all the tools around them are doing what the rest of the tools have been doing for the DOM since time immemorial: invent new, better ways that are only hampered by the underlying platform.