I don't think it's a bad thing for Facebook to take this obviously good idea from Google and adopt it themselves. It seems that the only outcome is a better experience for users.
Great news. I just upgraded our app to 0.14-rc1 last week and particularly enjoy "refs" being direct references to the DOM nodes. Can't wait to move some of our stateless components to functional.
Cool idea. I had a tiny issue where the leaves on the Meal Plan box overlap the corners of Monday and Sunday, meaning you can't drag in these areas. You can sort it out with:
Lettering.js recently merged some great accessibility code[1] that improves UX for screen readers by adding ARIA attributes. Each targeted element is given an aria-label with the original content, and each created span is marked with aria-hidden to avoid having the reader pause at every element. Would you consider implementing something similar for screen readers?
[0]: https://twitter.com/alexstamos/status/656582605173858305