• # May 19, 2013 at 11:04 am

    I tried building a site in SASS. It was neat, I guess. However, my workflow didn’t benefit at all, and I didn’t appreciate having to download all these separate applications just to make it work.

    I build sites the simplest way I know how—with a browser, a text editor, and an FTP client. That’s all I really need. Am I *really* missing something here?

    At the end of the day, I just don’t see any point in preprocessors. Sure, I’d use SASS if it didn’t have to be converted to CSS. But I’m not keen on jumping through tons of hoops just to supposedly “save time”.

    Anyone with me?

    # May 19, 2013 at 11:43 am

    This reply has been reported for inappropriate content.

    I’m still not completely sold… and I don’t really see how it would save me time, “global search and replace” does the same as “variables”, for example…

    # May 19, 2013 at 1:07 pm

    This reply has been reported for inappropriate content.

    There’s nothing wrong with not using a pre-processor, but it can definitely be useful.

    I use it primarily for 3 things:
    1. Auto-create sprites
    2. I work in a pretty modular fashion and have a ton of separate files. I could create a bash script to concatenate them (which I have done before) but I find that easier. Useful for large websites/webapps
    3. I like that you can put media query within elements. It’s useful when used with point 2.

    width: 300px;

    @media (min-width: 768px){
    width: 700px;

    # May 19, 2013 at 4:25 pm

    Just use whatever if you feel comfortable using. There’s too much of every one copying each other I feel in this industry. Just do what is right for you as long as you follow best practices the way that you get there needs to be right for you.

    It’s like everyone using Sublime Text, I personally hate it, just can’t get passed the sidebar opening images etc.

    I personally love SASS and Compass, just saves so much time. Nesting alone for me makes it worth using. Sprite sheets in compass are also great.

    # May 19, 2013 at 4:39 pm

    Nesting is nice but it quickly results in overqualified selectors (adding weight and unwanted specificity), keeping that in mind I still use it. I started using Sass only weeks ago but I started to like it, mostly because of variables (in combination with color functions of Compass, I can change one color to change the whole appearance of a site) and extending placeholder selectors. Those are easy to use without the risk of inefficient CSS. I use some other functions too, but with care.

    I’m fine with using Sass, but I was fine with writing plain CSS too. So use whatever works for you ;)

    # May 19, 2013 at 6:24 pm

    > mostly because of variables (in combination with color functions of Compass, I can change one color to change the whole appearance of a site) and extending placeholder selectors. @CrocoDillon

    Exactly why I started using SCSS.

    # May 19, 2013 at 11:51 pm

    I couldn’t imagine going back to just CSS. I don’t have time to reply to this right now, but hopefully I can remember tomorrow!

    # May 20, 2013 at 2:28 am

    I also wanted to say that I wish SCSS/SASS would become a standard. When you can dynamically write code that effects simplicity and performance, that’s a game changer.

    Personally, there’s nothing more that I hate than writing CSS (and HTML). This makes it more interesting and fun.

    # May 20, 2013 at 2:48 am

    This reply has been reported for inappropriate content.

    I like being able to create a structure with folders and files, yet everything gets written into one larger CSS file. This helps me, personally, because it helps me keep things organized and makes it easier to walk away from a project and come back and not worry about what I was doing last.

    # May 20, 2013 at 3:34 am

    There are loads of benefits to using Sass even if you don’t make use of all of them it’s still worth using IMO. If you use an app like Codekit or Hammer it makes it really easy to set up and use too.

    I also like how you can split up your files it makes organising CSS much easier and codekit can then just minify it all down into one file.

    Can’t really see why you wouldn’t use it really. Sure everything it does you can do the old / long handed way but why make life harder than it needs to be.

    It also makes writing css3 easier dealing with the vendor prefixes.

    [This video first sold me](

    # May 22, 2013 at 1:26 pm

    I try to make my points about WHY preprocessors in a recent talk:

    # May 22, 2013 at 6:18 pm

    This reply has been reported for inappropriate content.

    This is a topic I’ve also been wondering about. I also submitted a question to Shoptalk to get some additional thoughts hopefully.

    One concern I have is longevity and how this works within teams.

    Let’s just say for example that I use SASS for a year and half. Then we end up with something far better/more powerful/flavor of the month and everyone switches to something else. You might now have sites using straight CSS, SASS and now this new thing. I’m kind of holding back watching it all unfold to make sure that as this evolves, whatever path I go down makes sense (kind of like Mootools versus jQuery).

    And then in teams, I’m really wondering about how this functions with multiple people. Let’s say you have a project worked on by people who use SASS but everyone has different mixins. Is that going to muck anything up? And then there’s the one guy that might come in and mess with just the CSS and the whole thing is hosed until you can go back and fix it through the preprocessor.

    Maybe I’m just not totally understanding how this all works and I’d be glad for someone to help point out a few of these scenarios.

    # May 22, 2013 at 6:39 pm

    I think even if you use SASS in it’s most simple form (variables, nesting etc) then it should still speed up your workflow. I’m not sure how it would slow you down – an app runs in the background and compiles the SCSS in to CSS almost instantly, most of these apps also have live browser reload which is way more convenient than having to refresh your browser every time.

    # May 22, 2013 at 6:58 pm

    @JoshWhite well for any personal stuff, I don’t see a good reason not to use it. As for the longevity, it’s a tool, you can’t wait around to see IF something else will come out. Even if when it does, you can then make the switch and any new project will be done with this new imaginary tool.

    As for using SASS/Less in team environment, your whole team needs to make the switch (at least the people working on any particular project that uses preprocessing). Using Version Control easily fixes the issue with multiple people working on same files.

    I found the talk by Nicole Sullivan to be more valuable than the one Chris did.

    # May 22, 2013 at 10:11 pm

    <--- This guy still doesn't use a preprocessor.. I don't know, i just find the need for one (personally speaking). Many people bring up good points about it, i just rather not use it.

Viewing 15 posts - 1 through 15 (of 39 total)

You must be logged in to reply to this topic.