6 comments

  • Mattan IngramMattan Ingram, 5 years ago

    I don't get why anyone would want to work in a single file, especially for a large and complex project with multiple developers. Even well commented it sounds like a nightmare. Just make sure you import your files in the correct order in your build system and you won't have any issues.

    I definitely can see the problems with nesting in SASS, but it's so easy to do that we just limit it to one level of nesting if absolutely necessary and it hasn't been too much of an issue.

    11 points
    • Bryant HughesBryant Hughes, 5 years ago

      Agreed.

      Even with a disclaimer that tries to nullify criticism as "opinion", that way of writing CSS is just bad advice.

      3 points
  • Stefan TrkuljaStefan Trkulja, 5 years ago

    "Fuck CSS, let’s rock"

    So edgy.

    8 points
  • Rick LanceeRick Lancee, 5 years ago

    Try working on a large scale project with multiple developers and one css file, yeah... good luck.

    6 points
  • John LeschinskiJohn Leschinski, 5 years ago

    This is the worst advice. Utter trash.

    3 points
  • Ed AdamsEd Adams, 5 years ago

    Remember, everyone: just because someone wrote it, doesn't make it true.

    I think there is no problem with keeping your CSS files in small manageable files if you use Sass' @imports. The only part I agree with is nesting, and even that I do think it has it's place in moderation, such as:

    .content .box .inner { p { font-size: 1.1em; } ul { padding-top: 1em; } ol { padding-top: 2em; } }

    Basically, I hate this stuff. It's harmful to new people who don't know any better and might blindly follow this advice and it's just annoying to veterans.

    2 points