Hacker News Reader

It might seem like a terrible idea now. But when it was first introduced, a) people were still trying to get CSS and Components to work together, React having made components quite popular; and (b) React was actually usable, compared to the complete mess it's become now, especially after they introduced hooks.

I switched to web components for all my personal work.

View on HN

But we already had things like tachyons css (tailwind precursor) and webpack css modules at the time that both offered static stylesheet solutions to that problem.

They weren't great either in hindsight.

But more importantly, we need to explore different paths to figure out what doesn't work. Things which seem like bad ideas in hindsight aren't bad experiments to run - otherwise we will all learn nothing.

I want to invest in web components because it seems to be the next step in downscaling complexity.

What's your experience with state management and data binding in Web components? Any suggestion?

Reply on news.ycombinator.com