The big takeaway here is interoperability. React is great, Angular was great for its time, etc, but if your company builds out all its UI components in a specific framework you're locked into that framework, so a lot of churn happens if you ever decide to try the newest hotness. It appears that all the major browser vendors are now in agreement on a Web Components spec so it's only a matter of time now before we have a good, standardized way of extending the web spec.
Well, yes, because web components are native to the browser, not some third-party library. In other words, I'd feel no more locked into Web Components than I feel locked into the current DOM API.
Sorry to break it to you, React is not great. Angular neither. They fill a void that they should have never had to patch up, and are flawed because of it.
The fact that the 'newest hotness' breaks your GUI each time is an alarming sign that something is very broken. Additionally you seem to be talking as if this won't continue to happen.
Your final point - I'll believe it when I see it. Along with webAssembly, in 10 years.
Comments
The big takeaway here is interoperability. React is great, Angular was great for its time, etc, but if your company builds out all its UI components in a specific framework you're locked into that framework, so a lot of churn happens if you ever decide to try the newest hotness. It appears that all the major browser vendors are now in agreement on a Web Components spec so it's only a matter of time now before we have a good, standardized way of extending the web spec.
Do you believe that you would never find yourself feeling "locked in" to the features/capabilities of Web Components?
Well, yes, because web components are native to the browser, not some third-party library. In other words, I'd feel no more locked into Web Components than I feel locked into the current DOM API.
Sorry to break it to you, React is not great. Angular neither. They fill a void that they should have never had to patch up, and are flawed because of it.
The fact that the 'newest hotness' breaks your GUI each time is an alarming sign that something is very broken. Additionally you seem to be talking as if this won't continue to happen.
Your final point - I'll believe it when I see it. Along with webAssembly, in 10 years.