3 ms·
> That is ridiculous. They've come from some impetus, derived by some individuals, and they obviously had a goal in mind. They are in a spec, they're being impl
by dmitriid 9y ago
> That is ridiculous. They've come from some impetus, derived by some individuals, and they obviously had a goal in mind. They are in a spec, they're being implemented into browsers, they're emulated or polyfilled by various JS libraries, and they're being used by individuals around the web.
Yeah, yeah, yeah. Snake oil is also used by many people who say they know what they are doing.
And then you get presentations like this: https://www.youtube.com/watch?v=sK1ODp0nDbM https://www.youtube.com/watch?v=sK1ODp0nDbM where you learn that:
- people who implement the spec in the browser don't even have reference components
- people who try to sell the vision of WebComponents have to use pseudocode in their presentations because the APIs are horrendous
- the very same people casually drop things like "if we could only agree on how webcomponents should behave"
etc. etc. etc.
> I guess I'm simply not understanding what all the fuss is about. I think those busy building with React and friends might see no point to it, because why not just build it in React right?
Kinda. As someone else put it in the comment here: WebComponents are solving a problem no one has had for at least five years now. They are a solution in search of the problem. Worse still, they are entirely highjacked by Polymer.