Ratchet Performance
we're using `[foo*='bar']` quite a bit, and these selectors are really expensive. (they're actually the most expensive selector you can run)

Also, CSS evals from right to left (you probably know that) – so doing things like this doesn't actually scope the selector (perf wise makes them even more expensive):

``` CSS
.list [class*="button"]
```

The above is still running a universal selector `*` on the entire dom, then checking all attributes for class, then running an expensive regex on each class attr. Then, after it's done that, it checks the dom for list elements, and see's if any of the initial matched elements have a list parent.

I only bring this up because in the sample app i'm building rendering (on the phone) seems a little jank. Also (even without js) the scroll is horrible (though that may be unrelated). 

At anyrate, i think we should talk a look at css perf and see if there is anything we can do to improve it.

Also, I remember connor pointing out the other night that the slide.js perf on his phone was a little jank – which is something we should look at in the js.
