Explore >> Select a destination
|
You are here 
|
adamsilver.io | ||
| | | | |
kinsta.com
|
|
| | | | | Web Components are a standard way to create reusable and modular HTML elements without using a JavaScript framework. | |
| | | | |
lea.verou.me
|
|
| | | | | Disclaimer: This post expresses my opinions, which do not necessarily reflect consensus by the whole Web Components community. A blog post by Ryan Carniato titled "Web Components Are Not the Future" has recently stirred a lot of controversy. A few other JS framework authors pitched in, expressing frustration and disillusionment around Web Components. Some Web Components folks wrote rebuttals, while others repeatedly tried to get to the bottom of the issues, so they could be addressed in the future. When you are on the receiving end of such an onslaught, the initial reaction is to feel threatened and become defensive. However, these kinds of posts can often end up shaking things up and pushing a technology forwards in the end. I have some personal experience:... | |
| | | | |
www.zachleat.com
|
|
| | | | | A post by Zach Leatherman (zachleat) | |
| | | | |
daverupert.com
|
|
| | | Through stalking the #WebComponents hashtag and my Frontend Masters course, I'm privy to a lot of developers' first experiences with web components. There's a wide range of people digging in, but the most common first-time experience I come across is a developer coming from a classical component framework like React with JSX going straight to writing vanilla Web Components, becoming frustrated, and then deeming web components "not ready for primetime." | ||
