DEV Community

loading...

Discussion on: Why I don't use web components

Collapse
fokusman profile image
Ferit πŸŒŸπŸ•Œ

Isn't the push for Web Components mainly coming from one big browser vendor as some sort of "owning the web", as now developers moved on to non-Google tooling ?

I have the observation that the push for some web standards is also a commercial one. If only Chrome moves heavily into that direction and the rest (safari, firefox) is doing it more cautiously we will end up again in a weird situation where:

  • Hype driven developers produce applications only for Chrome,
  • the rest is getting "Move to Chrome" Banners...

It is not proven by data, yet I see many non-googlers sharing doubts about WC vs. Googlers talking about it as the "only good solution".

Collapse
equinusocio profile image
Mattia Astorino

This is a widley discussed spec. Chrome was just the first vendor implementing the spec v0 and made polyfills. Other vendors refused to implement a draft spec and they all waited for the v1. Now is widely accepted and implemented. No one forced people to use web components v0 or polymer...

Collapse
fokusman profile image
Ferit πŸŒŸπŸ•Œ

As I argued,

If a big Browser vendor who owns the biggest search engine, has one of the largest resources and blogs to push topics, pushes it, people will jump on that.
I used worked on multiple projects in the past with shadow dom v0 , native WCs and polymer.
Developers (Humans) are as much as everyone bound to their Bias, FOMOs etc. so it is not about actively forcing but passively pushing. I think you just undervalue the power of influence and hype in developer communities.

Thread Thread
equinusocio profile image
Mattia Astorino

I think hype is just a question of self-control. But you're right, not everyone can remain outside the hype-loop

Thread Thread
dmitriid profile image
Dmitrii 'Mamut' Dimandt

Including Google themselves. They re-implemented the whole of Youtube with v0 spec which now causes problems in some browsers.

Thread Thread
alangdm profile image
Alan DΓ‘valos

This is no longer true, youtube has already migrated to Polymer v3 which is based on the v1 web components standards so it no longer has any problems with the latest versions of all browsers (except edge but that's already not a problem as long as you use the chromium-based build)

Collapse
oenonono profile image
Junk

No. Specifications only become recommendations when MULTIPLE VENDORS implement them.

Every major browser vendor gave input to and agreed to Web Components.

The web community and web standards have been working on how to allow developers to extend HTML for at least 20 years.

That is what Custom Elements are.

Collapse
hyperpress profile image
John Teague

I mean the whole thing started with MS HTC and FF XBL. So the idea of web components goes way back.

Collapse
hyperpress profile image
John Teague

If Google had that much "push" we'd still be using HTML Imports. There's no Google conspiracy, and getting agreement to ship a change is daunting, it's open to public comments and suggestions.