+1 on making any class a mixin. That'd be an incredible feature, and was the reason lesscss has peaked my interest. Can't wait to be using that functionality in Sass.
Would be pretty cool if the 2 competing projects can share feature ideas and maybe even implementation code (like the rails/merb plugins). I see lesscss as a "less controversial" choice for designers, as it adds a couple of critical things to the css syntax, but things seem mostly look the same to CSS people. It'll come down to whether or not people like whitespace sensitivity, or would rather type in brackets & semicolons (though it seems like a no brainer decision to me). To a lesser extent, I like the variable syntax a bit nicer in lesscss. The @ seems a lot more natural than !, especially to ruby developers. Also, I think default SASS recommendations in docs & tutorials should focus more on the css style syntax (style: value) instead of the whacky initial sass syntax (:style value). I know a lot of people who saw that and got completely turned off by the project until they discovered the alternate syntax. On Jun 17, 11:16 am, Chris Eppstein <[email protected]> wrote: > ...may become *less* of an issue in future Sass releases... > pun intended? :-P > > Syntax matters from an adoption perspective, but not really much else. As I > said on hacker news, the power of sass is going to be increasingly visible > in its ability to allow design sharing via compass. The lesscss guy has > stated that he doesn't want those powerful features in less. > > Anyways, I'll be following the development of less and a free flow of > concepts between the projects is going to be a good thing for everyone. > Already I was talking to nathan about making any top level css class also > exposed as a mixin automatically. This would be a relatively trivial change > for us. > > Chris > > On Wed, Jun 17, 2009 at 10:57 AM, Nathan Weizenbaum <[email protected]>wrote: > > > > > Yeah, Chris and I have been talking about it. It seems mildly interesting, > > and it's always good to have competition, but at the moment the > > implementation seems quite immature, and it's not clear what benefits it > > offers over Sass (other than possibly syntax, which may become less of an > > issue in future Sass releases). > > > On Wed, Jun 17, 2009 at 10:46 AM, s.ross <[email protected]> wrote: > > >> Has anyone had a look it this project? Comments? Comparisons? > > >> Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
