Online since 1990 Yes! I started with Gopher. I do modern Web Component Development with technologies supported by **all** WHATWG partners (Apple, Google, Microsoft & Mozilla)
I am more and more of the opinion the terms Web Components and Frameworks should not be used in one article.
Web Components are just an API and some HTML additions.
Just like Set and Map are additions to the JavaScript language,
I have never seen an article where someone complains Map isn't the same as Redux.
I'm not comparing web components to frameworks. I'm suggesting that the underlying component model of frameworks will, in time, shift to utilize the APIs that comprise web components so they can focus on higher-level goals.
We don't use jQuery anymore because many of its features were "adopted" into the browser (e.g. querySelector). Standards take time. Now that we have a standard component model, frameworks that implement their own will start to be seen as redundant. They'll eventually shift gears into focusing on state management, routing, etc.
What's exciting about this future is we'll likely see a lot of new flavors for authoring components, but the end result will be standard custom elements that maintain interoperability.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I am more and more of the opinion the terms Web Components and Frameworks should not be used in one article.
Web Components are just an API and some HTML additions.
Just like Set and Map are additions to the JavaScript language,
I have never seen an article where someone complains Map isn't the same as Redux.
I'm not comparing web components to frameworks. I'm suggesting that the underlying component model of frameworks will, in time, shift to utilize the APIs that comprise web components so they can focus on higher-level goals.
We don't use jQuery anymore because many of its features were "adopted" into the browser (e.g. querySelector). Standards take time. Now that we have a standard component model, frameworks that implement their own will start to be seen as redundant. They'll eventually shift gears into focusing on state management, routing, etc.
What's exciting about this future is we'll likely see a lot of new flavors for authoring components, but the end result will be standard custom elements that maintain interoperability.