Cheap Sass Tricks

A204ca511ddee820957e715d6d363548?s=47 John W. Long
October 12, 2013

Cheap Sass Tricks

My talk on Sass Evangelism at SassConf 2013.

A204ca511ddee820957e715d6d363548?s=128

John W. Long

October 12, 2013
Tweet

Transcript

  1. 4.

    Timeline Nov 2006 Aug 2008 Jun 2006 Hampton & Nathan

    create Haml Sass is born Hampton Catlin’s first commit. Nathan joins in by December. Compass is born
  2. 5.

    Nov 2006 Aug 2008 Dec 2008 Eppstein joins Team Sass

    Jul 2009 Sass 2.2 released Sass is born Hampton Catlin’s first commit. Nathan joins in by December. Compass is born Becomes the “Stdlib” of Sass. Made by Chris Eppstein.
  3. 6.

    May 2010 Aug 2008 Dec 2008 Eppstein joins Team Sass

    Jul 2009 Sass 2.2 released Compass is born Becomes the “Stdlib” of Sass. Made by Chris Eppstein. Sass 3 released Adds support for SCSS.
  4. 7.

    May 2010 Apr 2011 Sass 3. 1 - Sass +

    Haml split Jul 2009 Sass 2.2 released Aug 2011 Rails 3.1 adopts Sass as the defacto way of writing CSS Sass 3 released Adds support for SCSS. Sep 2010 SassWatch is born Later finds gainful employment as @TheSassWay.
  5. 8.

    Apr 2011 Sass 3. 1 - Sass + Haml split

    Aug 2011 Rails 3.1 adopts Sass as the defacto way of writing CSS Jan 2012 Hampton creates libsass (a blazing fast C version of Sass) Jan 2012 SassMeetup Seattle Becomes a force for good all over the internets. Sep 2010 SassWatch is born Later finds gainful employment as @TheSassWay.
  6. 9.

    Aug 2012 Sass 3. 2 released Aug 2011 Rails 3.1

    adopts Sass as the defacto way of writing CSS Jan 2012 Hampton creates libsass (a blazing fast C version of Sass) Jan 2012 SassMeetup Seattle Becomes a force for good all over the internets. Aug 2012 SassCast Episode 1 Created by Dale Sande
  7. 10.

    Aug 2012 Sass 3. 2 released Oct 2013 SassConf 2013

    We finally have our own conference! Aug 2012 SassCast Episode 1 Created by Dale Sande
  8. 14.

    “There are several tools and frameworks out there at the

    moment which extend CSS to adopt a more programmatic syntax and function. It is my opinion that these are only really of benefit to people who haven’t yet mastered writing CSS properly... If you learn how to write your CSS sensibly... you will see little if any need for things like SAAS [sic] et al.” @csswizardry Harry Roberts January 2010
  9. 15.
  10. 16.

    “The same goes for things like rounded corners. I've a

    snippet in dreamweaver that I can pull out when I need to that gives me the code for rounded corners... This is a much more efficient way to handle the problem than having to write out the rule, and then declare it's variable and a further value, don't you think?” On mixins... – Russell B.
  11. 17.

    “Throughout your article, I constantly wondered why any of the

    things accomplished with Sass could not have been accomplished using CSS. The hallmark of a useful library or tool is that it solves a problem. The issue I still have with Sass after reading this article is that there doesn't seem to be a problem TO solve. You don't have to repeat style rules! You can combine CSS rules with inheritance. ” On solving a real problem... – Chris B.
  12. 18.

    “[What’s] Painful about CSS? Maybe the biggest pain is standards

    compliance between browsers, to which Sass is completely unrelated? Sass provides nothing but a complicated hand hold for beginners. More programmatic like? Why couldn’t they stick to a standard set of syntax rules? What is it with using a ‘!’ c’mon” On painful CSS? – Ddd
  13. 27.

    Pro tip — “If your CSS is complicated enough to

    need a compiler or pre-processor, you’re doing it wrong!” Andrew Clarke @malarkey
  14. 28.

    “I once wrote that there was no need to use

    a CSS pre-processor like LESS or Sass. I was wrong. Very sorry.” Andrew Clarke @malarkey
  15. 30.

    ✦ Showing off cool things ✦ Building frameworks (Compass, Bourbon,

    Foundation) ✦ Blog posts & articles ✦ Speaking at events ✦ Being friendly to newbies What has worked well?
  16. 47.
  17. 48.