27 comments

  • Jeremy StewartJeremy Stewart, almost 6 years ago

    Sooner or later they all switch to SCSS.

    10 points
  • Mark Otto, almost 6 years ago

    Hi, happy to talk about this more if y'all are curious. <3

    9 points
    • Mike Johnson, almost 6 years ago

      What is your opinion on @at-root directive? Does it help organization/readability or does it make code unnecessarily verbose?

      0 points
      • Mark Otto, almost 6 years ago

        @at-root sounds like a feature that's designed to compensate for less than ideal coding practices. Definitely could be a recipe for disaster with name collisions and an unexpected output for your compiled CSS.

        The brilliant part of super simple, class-based approaches is that you have a much clearer sense of what gets sent to the browser. Any time you're changing those expectations is an opportunity to hit a bug or snag down the line.

        1 point
    • Surjith S MSurjith S M, almost 6 years ago

      How difficult is to keep the Less version also? As, we have a Sass port currently, Will there be an Official Less port for v4?

      I heard that you've got friends at Less, Did you talk them about this? What was their response?


      I also like to see a detailed documentation on how to use the Bootstrap SCSS with our Custom SCSS without affecting the next BS update. like some modular way to follow when customizing Bootstrap.


      Last but not least, A Center Aligned Blockquote. 90% of website using center aligned Testimonials (may be with a circle img), like this http://dunked.com/

      Thanks for your time & effort!

      0 points
      • Mark Otto, almost 6 years ago

        I don't think it'd be difficult, just time consuming. To start, I don't think we'll have an official one at launch. I don't have the time to do both, and I don't think the folks on our team do either.

        We didn't talk to anyone at Less about this. The move has been done for several months now. Since we did the port, I had a feeling we'd make the move for v4. PostCSS was super tempting, but that was too large a departure I thought for one major version.

        The Sass team working on Bootstrap will likely help out with any docs stuff on our end. Hope we don't screw any of that up :).

        And I'll consider the centered blockquote :).

        0 points
  • Sacha GreifSacha Greif, almost 6 years ago

    Pretty cool. I feel like we finally have an answer to the LESS vs Sass/SCSS debate.

    3 points
    • Mark Otto, almost 6 years ago

      Both are so similar for the most used features that I honestly don't see too much of a debate. It's more about build tools, processes, and dependencies I think—e.g., asset pipeline, Ruby vs C, etc.

      4 points
      • Sacha GreifSacha Greif, almost 6 years ago

        Yeah, I meant "debate" more in the sense that it was hard to answer the "which one should I use?" question precisely because they were so evenly matched.

        I feel like Bootstrap switching to SCSS might just be the edge it needed to win out. Of course, now the "debate" will be SCSS vs PostCSS… ;)

        2 points
      • Ed AdamsEd Adams, almost 6 years ago

        So, if you think that LESS and SCSS are nearly the same in most respects, why make the switch? Not trying to be standoffish, just curious.

        1 point
        • Mark Otto, almost 6 years ago

          Popularity is a big one for me. The former seems pretty clear to me—Sass is more widely known and used. Plus, there's more of a community (or communities) around it with all the Sass conferences and meetups. Less, not so much it seems.

          I like Sass's syntax for things, too. The explicit @mixin name-of-mixin {} for example is nice in that it doesn't look like malformed CSS when you do .element { .another-element(); } in Less. That also makes it easier to explain to beginners in my mind. Although I do really like that "everything is a mixin" in Less with that, being explicit in your CSS is kinda what makes good CSS good.

          3 points
  • Norm Sheeran, almost 6 years ago

    While we are on the subject of SCSS is it possible to compile in the browser for developing? I'm guessing some JS to parse it prior to it being loaded. I Googled but couldn't get a definitive answer.

    1 point
  • Zach SegalZach Segal, almost 6 years ago

    TL:DR for those unaware, what is SCSS?

    1 point
    • Marc EdwardsMarc Edwards, almost 6 years ago

      http://sass-lang.com

      And, more specifically:

      There are two syntaxes available for Sass. The first, known as SCSS (Sassy CSS) and used throughout this reference, is an extension of the syntax of CSS3. This means that every valid CSS3 stylesheet is a valid SCSS file with the same meaning. In addition, SCSS understands most CSS hacks and vendor-specific syntax, such as IE’s old filter syntax. This syntax is enhanced with the Sass features described below. Files using this syntax have the .scss extension.

      http://sass-lang.com/documentation/file.SASS_REFERENCE.html

      4 points
  • Andy LeverenzAndy Leverenz, almost 6 years ago

    Good!

    0 points
  • Floyd WilliamsonFloyd Williamson, almost 6 years ago (edited almost 6 years ago )

    Glad you guys (and gals!) chose to use SCSS. It's the right balance between vanilla CSS and Sass/LESS.

    0 points
  • Norm Sheeran, almost 6 years ago

    Hey Mark,

    This might be a dump question, but do you still plan to ship bootstrap 4 in a vanilla CSS format as well as SCSS?

    I know I could just process this myself from the SCSS, just curious.

    0 points