Once Sass 3 is fully released, the website will reflect the fact that SCSS is the primary syntax.
On Fri, Apr 16, 2010 at 2:05 AM, Adam Hooper <adam.hoo...@gmail.com> wrote: > I feel like documentation could go a long way here. In reading about > the new change, I saw that there's SCSS, CSS and Sass and they all do > different things... > > ...but I never learned what I should use. > > Sure, call me uncreative, boring, or just plain stupid. But I feel, as > an end-user, other people are better at making the decision than I am. > I just want to know the best practice and, well, practise it. > > So I would be much less confused if the website and docs said, > front-and-centre, what syntax I should use. > > Adam > > On Wed, Apr 14, 2010 at 2:33 AM, Eric Meyer <eriii...@gmail.com> wrote: >> I'm not sure why anyone has strong opinions on this. No one is losing >> anything. At all. Nothing is being lost here. If you like Sass syntax, >> the addition of Scss has absolutely no effect on you. If you like Scss >> syntax, you can now use it happily. In the meantime, all of us get to >> write our stylesheets with the power of Sass and Compass. If you want >> to have a battle over the relative merits of white-space, go fight >> with the authors of CSS. >> >> It's simple: The mission of Sass/Compass is to extend CSS >> functionality with the power of abstraction. >> >> That's all. Syntax isn't and won't be the focus of this project. >> They're not trying to build 'the ideal css-replacement' syntax, >> they're trying to extend the power of css as well as possible in any >> given syntax. >> >> Alternative syntax is a happy by-product of abstraction. Different >> frosting for different occasions. One syntax allows you to add Sass >> power almost unobtrusive to your CSS. That's awesome. The other allows >> you to use an entirely new, simplified white-space syntax instead. >> Double bonus for those who like it. Both are useful in different >> cases, and both pass on the same power of abstraction. But it's all >> entirely a bonus. Use the one you like and move on. It doesn't matter >> how many users use which one or which is 'superior' - they're both >> totally cool and useful in their own ways. >> >> If you're scared that you might have to use a syntax you don't like, >> you obviously haven't made the upgrade yet. I've converted all of Susy >> to Scss, and updated several projects to use that new Susy, and I have >> still barely even looked at any Scss. I haven't written a single line >> of it. It all just works. This upgrade is slicker than you can >> imagine. >> >> Nathan and Chris blow my little designer mind. >> >> Now let's get back to sharing cool design patterns with this sweet >> tool they've built. I don't care how you write it, I just want mixins >> that make my sites better without me working harder. >> >> Cheers, >> Eric >> >> >> >> On Apr 13, 3:28 pm, Rhett Sutphin <rhett.sutp...@gmail.com> wrote: >>> Hi Richard, >>> >>> On Apr 13, 2010, at 4:07 PM, Richard Aday wrote: >>> >>> > No I am not trolling. I just want to highlight that I don't think >>> > learning to use white space is hard to do. However, I respect your >>> > argument that it "looks like CSS", but am worried that anyone who is >>> > going to learn SCSS could have just learned Sass instead. >>> >>> I tend to agree with you emotionally -- I've never understood the >>> reflexive hate that whitespace-sensitive languages get (not just Haml/ >>> Sass but python, too). However, reading this and other mailing lists, >>> it's clear that that hate isn't going away. The immediate buzz that >>> the CSS-similar-but-otherwise-just-like-Sass language LESS got upon >>> its introduction _last year_ is further evidence against the >>> assumption that anyone who would consider using SCSS would just as >>> easily use Sass. >>> >>> Sass and Compass are both great tools. It seems to me that Nathan and >>> Chris are making changes that will help them become more widely used >>> without losing any of their goodness. I don't see any reason to worry. >>> >>> Rhett >>> (A happy Haml/Sass user since 2007 or so) >>> >>> >>> >>> > On Tue, Apr 13, 2010 at 1:37 PM, Chris Eppstein >>> > <ch...@eppsteins.net> wrote: >>> > Are you trolling? >>> >>> > On Tue, Apr 13, 2010 at 1:28 PM, Richard Aday >>> > <richard.a...@gmail.com> wrote: >>> > I dont think we have any hard evidence to prove that by pushing SCSS >>> > we are going to gain any users. Any one interested in Sass could >>> > figure out the indentation based syntax easily. Seriously, how long >>> > would it take... 10 minutes??... >>> >>> > On Tue, Apr 13, 2010 at 10:47 AM, Nathan Weizenbaum >>> > <nex...@gmail.com> wrote: >>> > The Sass docs probably won't have such a toggle, though. And yes, this >>> > probably will mean that the indented syntax will have fewer users, and >>> > thus fewer bug reports etc. However, it will still be mentioned in the >>> > reference and on the website, if not featured prominently, and I'm >>> > confident that enough people will continue using it to keep it alive. >>> >>> > On Tue, Apr 13, 2010 at 10:29 AM, Suno Ano <suno....@sunoano.org> >>> > wrote: >>> > > Wincent> So the new syntax is more "approachable" because it will >>> > be >>> > > Wincent> more familiar, but by using it as the default syntax in >>> > the >>> > > Wincent> reference, >>> >>> > > Chris indicated that in fact the docs will have a toggle to switch >>> > > between the twohttp://bit.ly/9zyNUP >>> >>> > > -- >>> > > You received this message because you are subscribed to the Google >>> > Groups "Haml" group. >>> > > To post to this group, send email to h...@googlegroups.com. >>> > > To unsubscribe from this group, send email to >>> > > haml+unsubscr...@googlegroups.com >>> > . >>> > > For more options, visit this group >>> > > athttp://groups.google.com/group/haml?hl=en >>> > . >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Haml" group. >>> > To post to this group, send email to h...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > haml+unsubscr...@googlegroups.com >>> > . >>> > For more options, visit this group >>> > athttp://groups.google.com/group/haml?hl=en >>> > . >>> >>> > -- >>> > -Richard Aday >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Haml" group. >>> > To post to this group, send email to h...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > haml+unsubscr...@googlegroups.com >>> > . >>> > For more options, visit this group >>> > athttp://groups.google.com/group/haml?hl=en >>> > . >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Haml" group. >>> > To post to this group, send email to h...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > haml+unsubscr...@googlegroups.com >>> > . >>> > For more options, visit this group >>> > athttp://groups.google.com/group/haml?hl=en >>> > . >>> >>> > -- >>> > -Richard Aday >>> >>> > -- >>> > You received this message because you are subscribed to the Google >>> > Groups "Haml" group. >>> > To post to this group, send email to h...@googlegroups.com. >>> > To unsubscribe from this group, send email to >>> > haml+unsubscr...@googlegroups.com >>> > . >>> > For more options, visit this group >>> > athttp://groups.google.com/group/haml?hl=en >>> > . >>> >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Haml" group. >> To post to this group, send email to h...@googlegroups.com. >> To unsubscribe from this group, send email to >> haml+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/haml?hl=en. >> >> > > > > -- > My Website: http://adamhooper.com > My Blog: http://adamhooper.com/blog > My Twitter: http://twitter.com/adamhooper > Graph News: http://graphnews.ca > > -- > You received this message because you are subscribed to the Google Groups > "Haml" group. > To post to this group, send email to h...@googlegroups.com. > To unsubscribe from this group, send email to > haml+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/haml?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to h...@googlegroups.com. To unsubscribe from this group, send email to haml+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/haml?hl=en.
