4 ms·
For me a big part is that global CSS doesn’t match component based web applications as well. Coordinating global class names becomes a pain quickly. Then you mo
by mtsr 2y ago
For me a big part is that global CSS doesn’t match component based web applications as well. Coordinating global class names becomes a pain quickly. Then you move to scoped CSS and suddenly CSS doesn’t add much anymore.
- naasking 2y ago> Coordinating global class names becomes a pain quickly. In other words, CSS class names are the new global variables. I like that framing. Everything old is indeed new again.
- bryanrasmussen 2y ago>Coordinating global class names becomes a pain quickly. However scoped css variables does add quite a lot. So I'm thinking that can't be the scoping you were thinking of?
- ttfkam 2y agoBetter not to think of it as global variables and more like annotations for cross-cutting concerns. That said, don't blame CSS just because React treated it like a second class citizen. Try Svelte. Matches the components there perfectly. It really is amazing to use a web framework that doesn't hate the platform it's written for.