3 ms·
They are not a solution in search of a problem. They have a very clear problem statement, it's hard to orchestrate reusable front-end code. React's problem stat
by ehnto 9y ago
They are not a solution in search of a problem. They have a very clear problem statement, it's hard to orchestrate reusable front-end code. React's problem statement is roughly the same, but react seeks to provide more structure and functionality to the foundation of web components. The WebComponent spec is just trying to formalise that foundation.
- dmitriid 9y ago> They have a very clear problem statement, it's hard to orchestrate reusable front-end code. I'd love to see that problem statement written anywhere in any of the webcomponent-related specs or sites. If it were true, they would not have such cumbersome APIs, for example. On the contrary, WebComponents, as they turn out to be, realise next to none of their original goals: https://fronteers.nl/congres/2011/sessions/web-components-and-model-driven-views-alex-russell https://fronteers.nl/congres/2011/sessions/web-components-an... > but react seeks to provide more structure and functionality to the foundation of web components. React has nothing to do with web components. Until less than a year ago React team was set against WebComponents in any shape or form: https://docs.google.com/document/d/1QZxArgMwidgCrAbuSikcB2iBxkffH6w0YB0C1qCsuH0/edit https://docs.google.com/document/d/1QZxArgMwidgCrAbuSikcB2iB... What React was, and is, is a library with a specific goal that solved a specific problem, and it's basically this: "Build encapsulated components that manage their own state, then compose them to make complex UIs." No one really knows what WebComponents are, and what problems they solve. I know what Polymer is and what it attempts to solve though.
- ehnto 9y ago> No one really knows what WebComponents are 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. > I know what Polymer is and what it attempts to solve though. The WebComponents spec is admittedly lacking a full feature set to truly enable "Encapsulated Components" but with really not very much work ( https://bitbucket.org/polylab/polyblocks https://bitbucket.org/polylab/polyblocks ) you can get pretty close. 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? But not everything needs to be a highly orchestrated complex UI, and in those circumstances I still want to be able to re-use my frontend code.
- 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.
- spankalee 9y ago> "Build encapsulated components that manage their own state, then compose them to make complex UIs." uh, this applies to Web Components too. In what way do you think they're different?
- dmitriid 9y agoI have no idea what the purpose of WebComponents is anymore. Any and all of their original goals [1] are either not there anymore or solved in much better ways than whatever specs have become. Right now the narrative is "build reusable components that you can use anywhere regardless of library". We've been using jQuery components in our React projects for years, so the fuss is largely overrated. And since the vast majority of components are extremely highly Polymer-specific, good luck figuring out how to work with their components, it's no better than figuring out how to hook up a jQuery component. [1] https://fronteers.nl/congres/2011/sessions/web-components-and-model-driven-views-alex-russell https://fronteers.nl/congres/2011/sessions/web-components-an...