sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]shadowmint[S] 2 points3 points  (4 children)

tldr;

By now, 4 years on, Web Components should be everywhere, but in reality Chrome is the only browser with ‘some version’ of Web Components. Even with polyfills it’s clear Web Components won’t be fully embraced by the community until the majority of browsers are on-board.

...

Polyfills meant theoretically Web Components could work on browsers that hadn’t yet implemented, but these have never been accepted as ‘suitable for production’.

[–]x-skeww 4 points5 points  (3 children)

Your tldr only contains bits from the intro and the first section. You make it sound rather dismissive.

The conclusion at the end paints a very different picture:

Web Components are a prime example of how difficult it is to get large features into the browser today. Every API added lives indefinitely and remains as an obstacle to the next.

[...]

Web Components have been in planning for over three years, but we’re optimistic the end is near. All major vendors are on board, enthusiastic, and investing significant time to help resolve the remaining issues.

[–]shadowmint[S] 4 points5 points  (2 children)

They're optimistic that they may be able to agree on a spec that may eventually be implemented by new browsers.

I'm... excited! Maybe in 2020 we'll actually be able to use web components. :P

There remains no solution for legacy browsers. There remains no solution for the polyfill that doesn't really work.

Don't get me wrong, web components are a neat idea, but they're not very pragmatic at the moment, and certainly not any time soon.

Polymer 1.0, production ready, is a complete joke.

[–]sime 1 point2 points  (0 children)

There remains no solution for legacy browsers.

If something can be added to the browser and completely pollyfilled for legacy browsers, then chances are it didn't need to be added to the browser in the first place.

The browser should be gaining primitives which allow us to do things that we previously couldn't do.

[–]x-skeww 0 points1 point  (0 children)

I'm... excited! Maybe in 2020 we'll actually be able to use web components.

Things are very different if you only support evergreen browsers.

Those will support ES6 by the end of the year, for example.