[GreenSock ReactJS components needed]

I'm glad there are ways to make it work with gsap, but I don't see the points Jack made being questioned.

 

I agree about the react "way of thinking" being more pleasant to the developer tho: inmediate mode, you don't have to think too much about edge cases, etc. But it comes at a price and with its own set of drawbacks.

 

Anyway I hope someone can post some examples, performance comparisons, etc, so we all can get a better understanding of all the particularities.

[GreenSock ReactJS components needed]

1. People often say they want to use React because of its performance, but from what I can tell, the way animations would have to be done in React is quite the opposite - it'd be much more expensive. We're not "allowed" to set properties directly on the animated element (fast); instead, we've gotta make everything run through React (introducing a middle-man that slows things down). And/or if we've gotta hook into the React lifecycle methods, each time a render() happens we'd have to revert all the stuff that the tween was doing, record the progress of that tween, let React do its render, create a new tween and seek() to that original position that the in-progress tween was at. This is *NOT* good for performance. Why are we doing this again? What are the benefits? Isn't one of the primary goals **performance**? 

 

In my opinion react is popular right now because it solves some of the problems of client applications in a different way, and on some specific situations this can be beneficial.

A lot of us who use GSAP all we care about is performance and having control of what out application does, that's why we end up just using vanilla javascript (or maybe es6), structuring our application in a mv pattern with no framework or a very minimal one (backbone, etc).

 

If you want the best performance and control over your animations and application behavior react is not the best choice.