Kyle Simpson

should we pick up some tricks/optimizations from Ramda?

3

Some interesting things from Ramda to consider adding to FPO: * `_arity(..)` is used to create a function with a proper `.length`, from the results of utils like `curry(..)`, etc...

ch4 composition: add not about composition being "associative"

1

```js compose(compose(fn3,fn2),fn1) ~=~ compose(fn3,compose(fn2,fn1)) ```

just like the title says.

Minor general optimization (but will happen a lot with grips-css): ``` js m = m ? m : 5 ``` can be optimized to: ``` js m = m ||...

Consider: ``` css #box1 { color: red; font-weight: bold; } #box1, #box2 { color: green; } #box1 { background-color: blue; font-weight: normal; } ``` Currently, the first `#box1` ruleset would...

finally get this packaged and released. duh.

Not exactly what you're thinking, probably. Adding sourcemap support means that `grips.render(..)` would be able to accept a sourcemap to map the line/column values reported in any errors back to...