Dec 17, 2011
9 notes
css

The problem with CSS pre-processors

I’ve been considering to use a CSS pre-processor like SASS, LESS, Stylus, etc, for a very long time. Every time someone asked me if I was using any of these tools/languages I would say that I’m kinda used to my current workflow and I don’t really see a reason for changing it since the problems those languages solves are not really the problems I’m having with CSS. Then yesterday I read two blog posts which made me reconsider my point of view so I decided to spend some time today studying the alternatives (once again) and porting some code to check the output and if the languages would really help to keep my code more organized/maintainable and/or if it would make the development process easier (also if they evolved on the past few years).

  1. webfocuspinas reblogged this from carnotaurus
  2. carnotaurus reblogged this from decodering and added:
    I’m happy enough to use NotePad++ or VS2010 - You’re ok if you know what you are doing. An over-reliance upon tools...
  3. lindseykirkbride reblogged this from decodering and added:
    This post does an excellent job at summing up my own feelings about pre-processed CSS. Most of the benefits of something...
  4. tenshou reblogged this from decodering and added:
    at least someone still has some common sense, exactly what I feel about these pre-processors and CoffeScript and co....
  5. decodering posted this
About
Curious about code, mad about markup.* Subscribe via RSS.