5 ms·
> Now that I can leverage Web Components, I don't see a real need for React as the browser is very capable. Except for the long list of issues that WC proponen
by dmitriid 4y ago
> Now that I can leverage Web Components, I don't see a real need for React as the browser is very capable.
Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728
- mathgladiator 4y agoDamn, now I have to pretend those don't exist. I have to investigate how it breaks a11y as that seems to the the core killer in my case. How does that list square with https://shoelace.style/ https://shoelace.style/ ?
- dmitriid 4y agoThe linked tweet in the linked tweet gives one such example: https://twitter.com/sarahmei/status/1198069119897047041 https://twitter.com/sarahmei/status/1198069119897047041 I remember there being more, but I can't remember the links off the top of my head (and on mobile).
- ramesh31 4y ago>Except for the long list of issues that WC proponents pretend doesn't exist: https://twitter.com/Rich_Harris/status/1198332398561353728 https://twitter.com/Rich_Harris/status/1198332398561353728 This is the sad reality for web components. You end up needing so many libraries to do basic things that a framework would handle, that your project just becomes a defacto custom framework.