Explore >> Select a destination
|
You are here 
|
nolanlawson.com | ||
| | | | |
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: after I published my 2020 post titled "The failed promise of Web Components" which also made the rounds at the time, I was approached by a bunch of folks (Justin Fagnani, Gray Norton, Kevin Schaaf) about teaming up to fix the issues I described. The result of these brainstorming sessions was the Web Components CG which now has a life of its own and has become a vibrant Web Components community that has helped move several specs of strategic importance forwards. | |
| | | | |
augmend.com
|
|
| | | | | The Augmend blog covers information on our products as well as related areas in the AI + Collaborative developer tools space. Feel free to reach us on twitter if you have comments or thoughts on any of our posts. We love to hear from others passionate about this stuff! | |
| | | | |
hiddedevries.nl
|
|
| | | | | Hidde's blog about web accessibility, standards, HTML, CSS, JavaScript and more. | |
| | | | |
www.raymondcamden.com
|
|
| | | An experiment in showing and hiding slot content for web components. | ||
