Hacker News new | ask | show | jobs
by tomhallett 634 days ago
The statement I struggle with is "Web Components are mature now", not because of bugs per-se, but more of interoperability with the larger eco-system.

One example: if I want to use tailwindcss, then adopting web components comes at a cost/risk. While there are techniques like in this tutorial [1], you end up getting cut by the bleeding edge if you are not using Lit, you are using vite (based on comments), etc etc. (And the space moves so fast, I'd be afraid that any architectural differences between Tailwind and Web Components, might start to hurt me further in the future.)

1: https://www.youtube.com/watch?v=HwkXCYiRgtE

1 comments

I agree is Tailwind is easiest to use with global styles, and make the components use Light DOM in that case. I'd use Shadow DOM only when I need components to be fully isolated (includng styling and node visibility).