DEV Community

Discussion on: Why you should Stop using CSS Frameworks

Collapse
etienneburdet profile image
Etienne Burdet

Let's be realistic: after your 10th job where you need to implement CSS tabs (or cards with header/footer, button with hover etc.), what will you do? Either copy-paste from old project, or start having snippet with parameters. Same with utility classes, same with spacing and typography.

Either way, you won't do it from scratch every job. In wich case you're just better off using a framework that does it well, with all the accesibility, style coherence etc.

Also:

  • much less need to document your CSS for your workmates. Somebody has already done the job and probably did much better than you will ever do.
  • The structure of components and utility classes will be easier to learn for your team—if not by yourself. By many orders of magnitude.
  • Why is this combination of classes not working?", "Ho, I need to fix that. In the mean time you can do this hack". Never get fixed.
Collapse
theeasydev profile image
Uriel Bitton Author

Sure that's why i encourage developing your own css frameworks from designs you created yourself!

Collapse
amiamigo97 profile image
Ami Amigo

Exactly! That's why you need your own CSS system/framework

Collapse
jamespagedev profile image
James Page

The problem is there are so many styling frameworks out there now where every time I join a new team or start a new project the project lead wants a new style framework everyone has to use. This makes it feel like "I'm doing it from scratch ever time", and I have to learn css all over again in the way the framework dev(s) want me to learn it.

As long as developers use good patterns and clean code, their pieces should be re-usable throughout projects and css should really be enough. We used to believe in good code... what happened :(

Collapse
theeasydev profile image
Uriel Bitton Author

custom css always and forever :)