I'm watching a conference talk from 2016 that said: "We have a 5-year process trying to come up with a design for Web Components and it might be another few years" It's been a few years alright 🫠 - ThreadSky

chris.manson.ie • 10 days ago

I'm watching a conference talk from 2016 that said: "We have a 5-year process trying to come up with a design for Web Components and it might be another few years"

It's been a few years alright 🫠

Comments

engelman.nl•10 days ago

Web Components V1 are baseline since Microsoft decided to dump Edge and built it with Chromium
That was 5 years ago

chris.manson.ie•10 days ago

Sure the v1 spec might be baseline but that doesn't really tell the whole story. A lot of the recent blog posts about trying to legitimately use Web Components show the gaps in the design.

Until the user and developer ergonomics are fully dialed in the work isn't done 😔

engelman.nl•10 days ago

> Until the user and developer ergonomics are fully dialed in
> the work isn't done 😔

Then CSS is also not done

chris.manson.ie•9 days ago

I mean that's literally true 🤣 they are expanding the CSS spec all the time. The difference is CSS has had widespread adoption for 30+ years and web components are barely used, there are too many compromises to use them

joe.trusktr.io•9 days ago

I wouldn't say barely! Chrome stats shows that upto 20% of page loads use the `customElements.define` API over the past two years:

https://chromestatus.com/metrics/feature/timeline/popularity/1689

And this is without the type of hype trains that some other frameworks live off of.

joe.trusktr.io•9 days ago

(NSFW sidenote, be careful what websites you click through on that stats page, some of them will land you directly on porn site home pages)

engelman.nl•9 days ago

> Chrome stats shows that upto 20% of page loads
> use the `customElements.define` API over the past two years

18% and down from 20%

Those metrics still need clarification. TEMPLATE at 34%???

All Chrome Status Web Components tech metrics on one page:

https://web-components-usage-metrics.github.io/

chris.manson.ie•9 days ago

I mean how many of them are because Google themselves use it? 🤣 I would love to see % of websites like we tend to report jQuery and Wordpress stats

engelman.nl•9 days ago

> There are too many compomises in Web Components
> to use them

What are those compromises?

0.1 + 0.2 is 0.300000000004 in JavaScript

That is not even a compromise

Better not use JavaScript?

chris.manson.ie•9 days ago

I am not able to articulate those compromises very well, so I defer to someone else who has done it better 😂 @ryansolid.bsky.social

https://dev.to/ryansolid/web-components-are-not-the-future-48bh

Comments

Posting Rules

Reply