Keith Hörling
Keith Hörling
My team is using famo.us in light production and it's working well, visually stunning. Documentation is lighter at the moment and it helps to reach out on IRC & read...
np-- we're using this skeleton for client/server react rendering: https://github.com/DimensionSoftware/brunch-with-pb ...and overlaying the famo.us render atop, which is solid for small-to-mid-sized projects.
@jbremmer it's certainly not an ideal strategy since both react & famo.us render to the same DOM. Here's an example of react rendering the base HTML structure and famo.us is...
You may have already read my remarks on implementing famo.us modifiers in react: https://github.com/petehunt/famous-react/issues/1 A solid first step would be to fix the recursion strategy. There's also a pull request...
Ditto and applying this pull request didn't fix the issue for me: https://github.com/tonini/alchemist.el/pull/314 UPDATE: thank you @maruks, works perfectly after recompiling
+2 on "for x from y!"
The "from" keyword conflicts with existing range behavior from coffee. How about: for x of\* y!
@gkz since you were able to add contextual "for x from y" syntax, is it possible to use similar contexts and be more natural ES6: "for x of y"?
Possible to squeeze this into 1.4.1? :)
At this point everyone's voice has been heard. Gkz should decide the best syntax to move this forward.