Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefer Rekapi or GSAP #6

Closed
joelburget opened this issue Aug 3, 2015 · 2 comments
Closed

Prefer Rekapi or GSAP #6

joelburget opened this issue Aug 3, 2015 · 2 comments

Comments

@joelburget
Copy link
Contributor

I'd like to be told which to use because I have no prior knowledge to compare them on. Would be nice to have a note -- "If you don't know either Rekapi or GSAP, use Rekapi" (or GSAP).

@gilbox
Copy link
Owner

gilbox commented Aug 3, 2015

Well, it depends...

  • GSAP is much easier to configure. That's because rekapi has some additional configuration necessary (see spark-scroll-rekapi: lodash and underscore dependencies #3) beyond npm install spark-scroll-rekapi. If you're in the quick-and-dirty experimentation stage, use gsap to get up and running faster.
  • Although I haven't done any benchmarks I suspect that rekapi is marginally faster than GSAP. That's because rekapi was built around the concept of timeline-based animation and spark-scroll is all about treating the scroll position as a timeline.
  • GSAP supports animating SVGs. This is the main deciding factor for me. If I don't need SVG animation I prefer using rekapi although it's not a strong preference.
  • Rekapi and GSAP have different licenses.

joelburget added a commit to joelburget/react-spark-scroll that referenced this issue Aug 11, 2015
This is mostly a copy of the information from gilbox#5 and gilbox#6.
@gilbox
Copy link
Owner

gilbox commented Aug 12, 2015

closing this in light of PR #8

@gilbox gilbox closed this as completed Aug 12, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants