Compass or Bourbon (or other)?

[chriscoyier]

We kinda have to pick since we really need prefixing help.

[AaronLayton]

I'm up for Bourbon if it keeps all the prefixing nice and simple

[enjikaka]

Both are great from what I know. I have however only used Bourbon, since it's integrated by default in Prepos, and I was very pleased with it so I'd recommend it.

[jkneb]

Does Bourbon handles the correct -prefixes- inside "prefixed keyframes"? Which is the hardest part to deal with.

[chriscoyier]

I typically use Compass, but since Compass doesn't have animation/keyframe mixins at the moment in stable I'd lean toward Bourbon. Bourbon is built into CodeKit as well, for contributors wanting to use that.

[KittyGiraudel]

I personally prefer Compass since both Compass and Sass teams work together (while Bourbon is a side project). But it really doesn't make much difference in the end.

Actually, we should pick the one with the best support for @Keyframes animations.

[sindresorhus]

Autoprefixer

We shouldn't have to care about prefixes.

[paulirish]

autoprefixer is certainly my favorite for dealing with prefixes.

That then opens the question on if there is authoring advantage to variables and mixins beyond the prefix work.

edit: there is definitely authoring advantage.

[jkneb]

I vote for this.
http://bourbon.io/docs/#keyframes
Looks gorgeous.

[paulirish]

autoprefixer for those that don't know..

• it parses your CSS with a real parser
• it adds the prefixes you need
  • also adds prefixes to values. For example, to calc(1em + 5px) or to property names in transition.
• it uses caniuse prefix data so it's always up to date on which prefixes you can forget about.
  • it Removes outdated prefixes to clean libraries and legacy code.

We can do a Sass ➡️ autoprefixer workflow, no problem. I think that's a great idea.

[enjikaka]

autoprefixer sounds great!

[AaronLayton]

@paulirish I have no experience with autoprefixer, will this do keyframes aswell?

[KittyGiraudel]

So basically we just have to write Sass without thinking about prefixes and we're good?

[chriscoyier]

autoprefixer sounds good to me too, but I have no experience there. Does that mean we should/need to go Grunt?

[sindresorhus]

@AaronLayton yes
@hugogiraudel yes
@chriscoyier no: https://github.com/ai/autoprefixer#usage

[paulirish]

So basically we just have to write Sass without thinking about prefixes and we're good?

yes, you give autoprefixer this CSS:

and it generates

See https://github.com/ai/autoprefixer/tree/master/test/cases for more

---

grunt

nah not neccessary yet. we may evolve to a workflow that includes grunt, but let's add that barrier to entry when we need to :)

[jkneb]

Allright autoprefixer sounds great.

[joeybaker]

The only issue that I've run into with autoprefixer is sourcemaps. In that I don't know of a way to get both at the same time.

[paulirish]

The only issue that I've run into with autoprefixer is sourcemaps.

Good call.. That's being tracked here: postcss/autoprefixer#37

[benschwarz]

Yo. Autoprefixer. In master.

[chriscoyier]

We moved to Grunt to do it because there was to Guard plugin for autoprefixer. Probably better moving forward anyway.

Autoprefixer is being kinda whack though in what it's prefixing. We need to tweak the config to get it just right.

Will make new thread for that.