4 ms·

That seems like a rather bold statement without much reasoning behind it. What in particular makes you think that web components are "never happening"?

ropeadopepope 8y ago
This looks less than promising: https://caniuse.com/#feat=custom-elements https://caniuse.com/#feat=custom-elements
- tdumitrescu 8y ago
  That's the deprecated v0 spec, fyi.
  - ropeadopepope 8y ago
    https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=custom-elementsv1 doesn't look much better.
    - yesimahuman 8y ago
      It's unflagged in firefox nightlies. Edge needs to get with the picture but really they are the only one out at this point. The polyfils, while not ideal, work great and shouldn't be needed much longer. The mobile story here is actually quite strong, since all major mobile platforms have full support for it.
    - Klathmon 8y ago
      Out of the 4 major browsers, 2 major browser vendors have support for the base stuff, 1 has it behind a flag being tested ready to be turned on, and 1 doesn't have any support yet... That's pretty far from "not happening"
madeuptempacct 8y ago
I have been using Web Components on and off for about a year. They are a pain in the ass. Require polyfills, large file sizes makes me write hacks to load it conditionally, etc. Angular Elements just came out - they don't work as expected as well.
dmitriid 8y ago
Easy: web components have not implemented a single part of the original promise [1]. It's not Web Components that are happening, it's the dozens of frameworks required to make them work that are happening. Even mixpanel's library "does so by providing an easy-to-use state management and rendering layer built on Virtual DOM (the basis of the core rendering technology of React). Through use of the Snabbdom Virtual DOM library and first-class support for multiple templating formats" [2] Web Components are a very low-level extremely limited crummy DOM-based API that no one in their right mind wants to use. They are not happening. --- [1] https://fronteers.nl/congres/2011/sessions/web-components-and-model-driven-views-alex-russell https://fronteers.nl/congres/2011/sessions/web-components-an... [2] https://github.com/mixpanel/panel https://github.com/mixpanel/panel

ropeadopepope 8y ago

This looks less than promising: https://caniuse.com/#feat=custom-elements https://caniuse.com/#feat=custom-elements

tdumitrescu 8y ago
That's the deprecated v0 spec, fyi.
- ropeadopepope 8y ago
  https://caniuse.com/#feat=custom-elementsv1 https://caniuse.com/#feat=custom-elementsv1 doesn't look much better.
  - yesimahuman 8y ago
    It's unflagged in firefox nightlies. Edge needs to get with the picture but really they are the only one out at this point. The polyfils, while not ideal, work great and shouldn't be needed much longer. The mobile story here is actually quite strong, since all major mobile platforms have full support for it.
  - Klathmon 8y ago
    Out of the 4 major browsers, 2 major browser vendors have support for the base stuff, 1 has it behind a flag being tested ready to be turned on, and 1 doesn't have any support yet... That's pretty far from "not happening"

madeuptempacct 8y ago

I have been using Web Components on and off for about a year. They are a pain in the ass. Require polyfills, large file sizes makes me write hacks to load it conditionally, etc. Angular Elements just came out - they don't work as expected as well.

dmitriid 8y ago

Easy: web components have not implemented a single part of the original promise [1]. It's not Web Components that are happening, it's the dozens of frameworks required to make them work that are happening. Even mixpanel's library "does so by providing an easy-to-use state management and rendering layer built on Virtual DOM (the basis of the core rendering technology of React). Through use of the Snabbdom Virtual DOM library and first-class support for multiple templating formats" [2] Web Components are a very low-level extremely limited crummy DOM-based API that no one in their right mind wants to use. They are not happening. --- [1] https://fronteers.nl/congres/2011/sessions/web-components-and-model-driven-views-alex-russell https://fronteers.nl/congres/2011/sessions/web-components-an... [2] https://github.com/mixpanel/panel https://github.com/mixpanel/panel