Just to build on top of this, and syntax-aside, what about using frameworks like SMACSS, BEM, OOCSS, etc for organizational purposes? I've been hearing a lot about these especially lately and about their greatness for scalability and maintainability once implemented and relied on.
Re:Show HN: CSS Quality Guide
by lemonberry on Friday July 10, 2015 @05:08PM
(#9866706)
Aren't those approaches to css rather than frameworks? I believe you can use a framework and still use those approaches to css.
Do you have a particular framework you'd recommend?
It must really depend on what you're looking for/doing. My favorite is http://getskeleton.com/. I'm a noob, but I like that I can understand and completely customize the 400 lines of code (https://github.com/dhg/Skeleton/blob/master/css/skeleton.css) easily.
Re:Show HN: CSS Quality Guide
by armandososa on Friday July 10, 2015 @05:21PM
(#9866770)
I, personally, like foundation. Mostly because it's more barebones than Bootstrap, it's fairly easy to customise and it uses SCSS which I like better than Less.
On the other hand, it sometimes feels like its development has stalled, while Bootstrap future looks bright https://twitter.com/mdo/status/591364406816079873?lang=en
The major problems I've seen with frameworks is that people just use the default look or try to add customisations on top of the default CSS, overriding styles. I mean, that is just setting yourself up for a world of pain.
But most CSS frameworks are really, really flexible in the build stage. You can tweak a few variables that can dramatically alter the appearance of a stylesheet and give you an awesome base to build on. Pretty much for free.
If you do all the CSS from scratch you're anyway going to write at the least a reset, some base typographic styles, responsive stuff, and some kind of grid system. Why not use something that is widely used, peer-reviewed, and very customisable?