4 ms·

> There is an easier solution to this than Web Components - using a single framework. Yes, we all know how easy that is. I mean, really, come on -- that's not

> There is an easier solution to this than Web Components - using a single framework. Yes, we all know how easy that is. I mean, really, come on -- that's not realistic in any reality. EDIT: We all know the "n+1" standards XKCD joke, but the reality is that standards (HTML, CSS, HHTP, DNS, TCP, UDP, IP, etc.) brought us the fucking Internet, flawed as those standards may be. As I said, I'm cautiously optimistic that standardizing "custom DOM" will eventually get us to a standard slightly above raw HTML.

masiulis 9y ago
> I mean, really, come on -- that's not realistic in any reality. Huh? Most projects use a single framework in a project, sometimes two if they are migrating. If I had multiple frameworks in my project, sharing components between them would be the least of my problems. > standardizing "custom DOM" will eventually get us to a standard slightly above raw HTML I understand this sentiment, but DOM is irrelevant to front-end work right now. DOM is just a render target for frameworks, making DOM smarter changes nothing.