3 ms·
I don't actively follow web components, but as someone who follows the React space reasonably well, I don't get any sense that things are shifting towards web c
by travisd 5y ago
I don't actively follow web components, but as someone who follows the React space reasonably well, I don't get any sense that things are shifting towards web components (at least in the sense of replacing React). React's docs[1] argue that they solve different problems (obviously that's potentially biased, but I still find it reasonably compelling). I think the most likely outcome is that some things will be shipped as web component libraries that can be easily consumed within various frameworks (e.g., I could envision Stripe shipping a webcomponent library instead of a React specific library).
[1] https://reactjs.org/docs/web-components.html https://reactjs.org/docs/web-components.html
- okareaman 5y agoThis makes sense. I really like the idea of non-framework specific components so that's the route I'll take. I'm happy that option is growing in viability. Thanks.
- Andrej996 5y agoWeb Components will not replace frameworks, but enhance them. It doesn't matter which framework you use (current ones like Angular, React or Vue) or some future framework, web components work in ALL of them. They are currently supported by all modern browsers, and about IE11 its time to let go of that one.