Re:Web Components could replace frontend frameworks?
by benforreal on Thursday April 11, 2019 @09:10PM
(#19640977)
I'm glad to hear this take. I came from Angular v1 and got sick of the framework churn, so jumped over to Web Components around 2015/2016 instead of going React. I abandoned Polymer pretty quickly around v0.6 because things were changing too much and just went plain vanilla JS + Web Components. I've been building applications since then with just Web Components and couldn't be happier. Unfortunately I just don't have enough experience with React to debate any of these points - I guess I just have to leave it that React is a need I don't have.
Re:Web Components could replace frontend frameworks?
by KuhlMensch on Friday April 12, 2019 @07:33AM
(#19643846)
> In that sense, the killer app for Web Components is actually Design Systems, not SPAs.
My read too
Frankly, this has been transformational for our project and for our business. I'm completely sold.
One problem with the WC debate is people constantly compare the raw Web Component collection of APIs to a framework, when in reality, you'll add in libraries or extras on top of your Web Components to get similar functionality (like Stencil: http://stenciljs.com/), but you'll likely not build apps with them as much as you'll build components to share with others.
In that sense, the killer app for Web Components is actually Design Systems, not SPAs.
I disagree with the idea that Web Components replace your framework, however. They solve different problems! For Ionic as a cross-platform Design System, they are a major asset.