3 ms·
That isn’t really an argument for React or any other framework going out of fashion in the next few weeks though? It seems rather contrived to think that Web Co
by thomasfoster96 8y ago
That isn’t really an argument for React or any other framework going out of fashion in the next few weeks though? It seems rather contrived to think that Web Components are inherently better because they’re standardised. React isn’t using unstandardised browser features, and it’s not as though you’re not still reliant upon your chosen Web Components library being maintained in future.
- flowerlad 8y agoWeb Components are directly implemented by browsers so you don’t need a “Web Components library”. So yes they are inherently better because they work in every application and every framework. This universal compatibility and better reliability makes Web Components a better choice today for creating reusable components, than React.
- thomasfoster96 8y ago> Web Components are directly implemented by browsers so you don’t need a “Web Components library”. I mean a collections of components like Polymer. Unless you plan on maintaining everything yourself, both React and Web Components share the same problem here. > This universal compatibility and better reliability makes Web Components a better choice today for creating reusable components, than React. You can mix and match any and all frameworks and Web Components if you try want. And again: React and Web Components mostly solve different problems. One isn’t going to directly cannibalise the other. You can use both.