Explore >> Select a destination
|
You are here 
|
knowler.dev | ||
| | | | |
markdalgleish.com
|
|
| | | | | Web Components are going to fundamentally change the nature of HTML. At first glance, they may seem like a complicated set of new technologies, but ... | |
| | | | |
nolanlawson.com
|
|
| | | | | Web components are kind of having a moment right now. And as part of that, shadow DOM is having a bit of a moment too. Or it would, except that much of the conversation seems to be about why you shouldn't use shadow DOM. For example, "HTML web components" are based on the idea that | |
| | | | |
www.abeautifulsite.net
|
|
| | | | | A tweet-thread turned blog post that talks about custom elements. | |
| | | | |
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." | ||
