4 ms·
Doesn't the browser now have native web components and this will replace React as time continues?
by edmcnulty101 4y ago
Doesn't the browser now have native web components and this will replace React as time continues?
- lelandfe 4y agoYa, but you gotta roll your own process for the stuff React and co. provide easy methods to do. It's just a lot of boilerplate for small projects. I don't know if web components will really be a "library killer" in the same way browser APIs have done with jQuery. https://github.com/mdn/web-components-examples/blob/main/popup-info-box-web-component/main.js https://github.com/mdn/web-components-examples/blob/main/pop...
- dbxkcichhdfufu 4y ago
- Octoth0rpe 4y agoReact is about a whole lot more than just web components. It's also a strategy for state management, life cycle, etc. I don't expect web components will ever replace react, but I think it's possible we'll see a new generation of react-like competitors that use web components under the hood.
- collyw 4y ago> It's also a strategy for state management, life cycle, etc. As a backend dev who can do a bit of traditional style frontend, I fail to see the need for all this complexity. Most apps are running same database queries and displaying it on a webpage.