16. Downsides of libSass
● Binary files (os/hw dependent).
● Not a language many webdevs know.
● Slower to develop new features.
● Ecosystem fragmentation
17. Sass is more than a language
Sass is a community of web
developers sharing their best
practices, code, and tools for
writing CSS.
20. node-sass
● C++ ⇔ node.JS bridge
● npm install node-sass
● var sass = require(“node-sass”)
sass.render(...) // => CSS
21. What about Compass?
● Compass is not being ported to
libSass.
● The best parts of compass are
being recreated.
● Active Development
22. Sass modules as rubygems
Alright. Let’s do this.
npm modules
23. ● Distribute Sass modules via NPM
● Import Sass from modules
● Define Sass functions – in JS
● Global resolution of shared
dependencies.
● Deliver assets with the right URLs
Eyeglass
41. Eyeglass Spriting compared to Compass Spriting
● Works with multiple file formats
● Files can be in several
directories.
● No “Magic Import”
42. Take Aways:
● Use libSass. It’s ready.
● Use eyeglass to distribute Sass.
● No new features for Compass.
● node-sass-utils for writing Sass
functions in JS.
● Ruby Sass is not dead.
44. Why not Bower?
Bower is a “front end packager”.
● No conventions.
● No framework.
● Every bower package is a
snowflake - requires devs
to know internal structure.
❄
❄
❄
❅
❆
❄
❆
❅
❄ ❅
❄