SISirHound·Nov 30, 2015
Fundamentally, it works with every API you can stuff a number into. "Number" includes stuff like hex/rgb values and complex strings, too.
So yeah, it does work with React, however:
1) It will only do CSS value detection (stuff like prefixed values and transform value mapping) if you either give Popmotion a direct reference to the underlying DOM element as if you were using it normally, or manually set a CSS role on Actor init. This only becomes a problem when you're working with completely stateless components, but then it could be argued that stateless components shouldn't be responsible for their own transitions. This is because:
2) No JSX support. I've seen the Velocity React implementation and I'm not convinced this is the best API (if you haven't seen it, check it out: https://github.com/twitter-fabric/velocity-react) I wonder if the
Read the rest
drive towards JSX-everything isn't a misstep and that in some situations things that should be `params` are being made into JSX tags.
I don't have a wild amount of experience with React so I'd be interested in hearing your thoughts.
And thanks for your opinion on the pay structure, I think we're largely in agreement there. Good food for thought.