3 ms·

> I asked them if they were using a CSS framework at all and the response was "we are using React, we don't need one". This hurt my brain. I recently saw a vi

> I asked them if they were using a CSS framework at all and the response was "we are using React, we don't need one". This hurt my brain. I recently saw a video where a guy was claiming that people who had gone through a web development bootcamp (using React and the whole nine), where unable to make a basic hello world HTML file. When people don’t know the basics, it’s no wonder everything is over complicated. They were never taught how it could be simple.

ffsm8 2y ago
> This hurt my brain. Why? It's straight up correct. Sure, you could still use a css framework, but you really don't need to once you're using any frontend library. Each component comes with it's own styles, that makes the css framework redundant, as a component library gives you a better development experience with the same effect. Add a few global vars for theme colorings, default spacing etc and it becomes pretty straightforward to maintain a coherent UI even across repositories/teams (or distribute a tailwind config,works even better imo)
- al_borland 2y ago
  That’s assuming they are using a component library that has a common system for its styles. If their end result was an inconsistent UI, it doesn’t sound like they were. They could have been making their own components, or mixing component libraries, with inconsistent styles, based on whatever the first search result was for their need.
Spivak 2y ago
It's kinda right. React says manage complexity through encapsulation, CSS as intended to be used says impale straight through the layers via global namespace and a brittle rats nest of interdependency via the side-channel of selectors. CSS as simply a DSL for styling components and hooks into the layout engine like how other GUI frameworks work is fine, but you don't need a framework for that. We all generally agree that inheritance is hard to keep clean but in CSS it's venerated for some reason.

ffsm8 2y ago

> This hurt my brain. Why? It's straight up correct. Sure, you could still use a css framework, but you really don't need to once you're using any frontend library. Each component comes with it's own styles, that makes the css framework redundant, as a component library gives you a better development experience with the same effect. Add a few global vars for theme colorings, default spacing etc and it becomes pretty straightforward to maintain a coherent UI even across repositories/teams (or distribute a tailwind config,works even better imo)

al_borland 2y ago
That’s assuming they are using a component library that has a common system for its styles. If their end result was an inconsistent UI, it doesn’t sound like they were. They could have been making their own components, or mixing component libraries, with inconsistent styles, based on whatever the first search result was for their need.

Spivak 2y ago

It's kinda right. React says manage complexity through encapsulation, CSS as intended to be used says impale straight through the layers via global namespace and a brittle rats nest of interdependency via the side-channel of selectors. CSS as simply a DSL for styling components and hooks into the layout engine like how other GUI frameworks work is fine, but you don't need a framework for that. We all generally agree that inheritance is hard to keep clean but in CSS it's venerated for some reason.