Recent searches
Search options
Administered by:
New post:
The Good, The Bad, The Web Components
https://www.zachleat.com/web/good-bad-web-components/
A full crash course on the state of web components, where they fit in JavaScript frameworks landscape, and how to make use of them moving forward!
@zachleat Sorry if this doesn't make sense. I've read, and think I understood, your comprehensive blogpost, thanks. I run e.g. https://fixmystreet.com/ which uses a server-side framework, with added JS (though the slippy map still works without!). Could/should I add web components to this? Where would I start? When you say e.g. "Multiple instances of the same component need to repeat the same nested content" I'm like, yeah, that's fine, I have a server-side language to do that ;-)
@zachleat@zachleat.com@dracos yeah, I think you’re on the right track! JavaScript ecosystem folks sometimes complain that web components aren’t “full stack” out of the box, but that’s kinda what I was trying to get at in the post—to make a web platform feature full stack is a bridge too far. The full stackiness of the thing should live in library land—and we need more abstractions for that!