3 ms·

My biggest qualm with Sass is that it introduces a speed bump in my workflow compared to using plain CSS. This is due to the fact that I can use tools like CSS

My biggest qualm with Sass is that it introduces a speed bump in my workflow compared to using plain CSS. This is due to the fact that I can use tools like CSS Edit to create, edit, and verify my CSS all at the same time. If these tools also supported Sass I'd be all set.

aaronbrethorst 17y ago
Although it doesn't satisfy your 'no speed bump' test, you could still generate css files with CSSEdit and then convert them to Sass with css2sass. Certainly inelegant, but it could cut it. Also, just out of curiosity, why do you use CSSEdit? I'm guessing you probably write your HTML or Haml markup with Textmate and not Dreamweaver, right? Why do something different with CSS?
- jherdman 17y ago
  CSS Edit gives me instant feedback on my changes. It's not always easy to know how changes to your CSS will display. You have to think about all the rules that are in play, as well as the defaults of a given browser. HTML is much easier. You're just dealing with structure, so it's much easier to comprehend.
ThinkWriteMute 17y ago
My biggest problem with SASS is that it's turned into a full on programming language.
- nex3 17y ago
  This is an odd meme, and not really accurate. Yes, Sass has a few control structures that are not meant to be used in day-to-day stylesheet coding. But the language is wholly geared towards creating stylesheets, and every feature was added with that in mind. It doesn't contain any programming features for the sake of having programming features. Incidentally, it's also not Turing-complete.
  - ThinkWriteMute 17y ago
    I'm pretty sure it is Turning-Complete, and it's something they were heralding a few weeks back. Their goal is to be a programming language. Wikipedia: After its initial versions, Nathan Weizenbaum and Chris Eppstein have continued to extend Sass with SassScript, a Turing Complete scripting language used in Sass files. and http://wiseheartdesign.com/articles/2010/01/18/the-demise-of-css-why-sass-and-languages-like-it-will-triumph/ http://wiseheartdesign.com/articles/2010/01/18/the-demise-of...
    - chriseppstein 17y ago
      You're replying to the guy who writes Sass. He's right. It's not actually turing complete, but it could be made so with a relatively minor change. And I'm the guy who invented most of the programming facilities of Sass and I'll tell you, they're not very good programming tools -- but they're enough to make some really great stylesheets.
    - nex3 17y ago
      In order to be Turing-complete, Sass would have to have some way of reading and writing arbitrary amounts of memory. Since it has neither anonymous functions nor any sort of data structures, it can only read and write from pre-declared variables.
nex3 17y ago
We've tried to get the CSSEdit folks to support Sass, but so far they haven't been interested. I think the best way to get that is to have more users say they want it.
- alextgordon 17y ago
  I would guess that such a change would be too big to be economically viable. Sass would require a rewrite of all the parsing code, and a redesign of the GUI CSS editor. Unless Sass gains a considerable market share among Mac users, I doubt it'll happen. You're better off trying to convince them to include the necessary hooks in Espresso, if they add CSSEdit-style functionality to it.

aaronbrethorst 17y ago

Although it doesn't satisfy your 'no speed bump' test, you could still generate css files with CSSEdit and then convert them to Sass with css2sass. Certainly inelegant, but it could cut it. Also, just out of curiosity, why do you use CSSEdit? I'm guessing you probably write your HTML or Haml markup with Textmate and not Dreamweaver, right? Why do something different with CSS?

jherdman 17y ago
CSS Edit gives me instant feedback on my changes. It's not always easy to know how changes to your CSS will display. You have to think about all the rules that are in play, as well as the defaults of a given browser. HTML is much easier. You're just dealing with structure, so it's much easier to comprehend.

ThinkWriteMute 17y ago

My biggest problem with SASS is that it's turned into a full on programming language.

nex3 17y ago
This is an odd meme, and not really accurate. Yes, Sass has a few control structures that are not meant to be used in day-to-day stylesheet coding. But the language is wholly geared towards creating stylesheets, and every feature was added with that in mind. It doesn't contain any programming features for the sake of having programming features. Incidentally, it's also not Turing-complete.
- ThinkWriteMute 17y ago
  I'm pretty sure it is Turning-Complete, and it's something they were heralding a few weeks back. Their goal is to be a programming language. Wikipedia: After its initial versions, Nathan Weizenbaum and Chris Eppstein have continued to extend Sass with SassScript, a Turing Complete scripting language used in Sass files. and http://wiseheartdesign.com/articles/2010/01/18/the-demise-of-css-why-sass-and-languages-like-it-will-triumph/ http://wiseheartdesign.com/articles/2010/01/18/the-demise-of...
  - chriseppstein 17y ago
    You're replying to the guy who writes Sass. He's right. It's not actually turing complete, but it could be made so with a relatively minor change. And I'm the guy who invented most of the programming facilities of Sass and I'll tell you, they're not very good programming tools -- but they're enough to make some really great stylesheets.
  - nex3 17y ago
    In order to be Turing-complete, Sass would have to have some way of reading and writing arbitrary amounts of memory. Since it has neither anonymous functions nor any sort of data structures, it can only read and write from pre-declared variables.

nex3 17y ago

We've tried to get the CSSEdit folks to support Sass, but so far they haven't been interested. I think the best way to get that is to have more users say they want it.

alextgordon 17y ago
I would guess that such a change would be too big to be economically viable. Sass would require a rewrite of all the parsing code, and a redesign of the GUI CSS editor. Unless Sass gains a considerable market share among Mac users, I doubt it'll happen. You're better off trying to convince them to include the necessary hooks in Espresso, if they add CSSEdit-style functionality to it.