On Jun 17, 2009, at 12:11 PM, Chris Eppstein wrote: > So now that you know the answers, what would you say they are?
- WORKS OUT OF THE BOX with Rails, merb, Sinatra, Compass, Staticmatic, etc., etc. - WORKS OUT OF THE BOX as a standalone - Refactorable styles via abstraction (variables, expressions, ...) - Reusable styles via mixins - Clearly nested styles that exactly mirror your DOM at a glance - Readable error messages - Mature and tested, very active community -- look at the project activity and mailing list These sound like a start? Ideally, there is some synergy like that between rSpec and shoulda where all the good ideas merge and the energy from both come together in a good way. Steve > On Wed, Jun 17, 2009 at 12:07 PM, s.ross <[email protected]> wrote: > Well, the marketing from the lesscss site reads like this: > > Less uses existing css syntax. This means you can migrate your > current .css files to .less in seconds and there is virtually no > leaning curve. > > How many people know that beside the out-of-the-box, it-just-works- > with-your-framework Haml/Sass there is also this keen tool called > css2sass? Y'know, migrate your current .css files to .sass in > seconds and there is virtually no learning curve? > > Nathan/Hampton, no offense intended, but from the very first days of > Haml, the Web site has been extremely cool, but also somewhat opaque > with respect the the top-level benefits offered. People with short > attention spans (140 characters or fewer) just don't read past the > Haml-Haiku stuff. I'm a sucky designer too, but an ok writer. The > first three paragraphs of the lesscss Web site answer the question > "why should I care and how will it make my daily life easier?" > > I know the answer to these questions about Haml and Sass, but new > people flow into the community and it would be great to have a > simple executive summary for them. Even if it dumbs down the intent > and power of the tools, it will get people interested. > > Steve > > > On Jun 17, 2009, at 11:50 AM, Chris Eppstein wrote: > >> Thanks. >> >> Every time I look at a new programming language there's something I >> HATE about it. For C it was the need to have a semi-colon at the >> end of every line, for java it was the straight jacket they placed >> on me, for python it was the whitespace active syntax, for ruby it >> was the incredibly verbose begin/end. I got over all of it in a >> matter of hours or days. Except the java straight jacket -- >> seriously that blew. But that initial reaction can completely >> change the adoption rate which is why the more innovative >> technologies take longer to reach mainstream adoption, usually 5-6 >> years. Sass is only 2 years old -- just an adolescent technology >> really. Folks that dismissed sass a year ago are taking a second >> look recently and deciding it's worth using now. >> >> Even if Sass ends up being a "second place" technology like >> prototype to jquery, I still will be proud of it, because we're >> breaking ground and changing the way people think about design and >> and the maintainability of websites. >> >> The biggest hurdle that any new style syntax has is the need to >> compile it. To that end, making Sass embed-able within a web >> browser and fast enough that users don't notice it, will be a >> radical step towards mainstream adoption. This means having all >> kinds of boring things like W3C proposals, a published grammar, a C- >> based parser, and a spec suite to validate alternate >> implementations of sass as compliant, etc. >> >> Chris >> >> On Wed, Jun 17, 2009 at 11:20 AM, s.ross <[email protected]> wrote: >> >> >> On Jun 17, 2009, at 11:15 AM, Noel wrote: >> >> > >> > I think that part of the reason that less got so much attention >> has to >> > do with marketing. By that I mean they really have a nice site >> and it >> > is very easy to compare and contrast CSS with LessCss. >> >> Also a little Twitter love. You're right. It's hard to overstate how >> much marketing a technology does for it. Look at "Prototype is bad, >> jQuery is good." I just have to think some of that has to do with the >> community uptake of jQuery and how easy it is to find your way around >> their site and grab plugins. >> >> Kudos to Nathan and Hampton for the great ideas and to Chris for >> showing the world how insanely cool Sass can be in application. This >> is not to neglect everyone else who's contributed to the project. >> >> >> >> >> >> > > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
