3 ms·
> "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 yo
by 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...