Alternatives to GreenSock logo

Alternatives to GreenSock

CreateJS, BabylonJS, anime.js, Lottie, and three.js are the most popular alternatives and competitors to GreenSock.
72
95
+ 1
0

What is GreenSock and what are its top alternatives?

It is a JavaScript library for creating high-performance animations that work in every major browser. It delivers advanced sequencing, reliability, API efficiency, and tight control while solving real-world problems. It works around countless browser inconsistencies.
GreenSock is a tool in the Javascript UI Libraries category of a tech stack.
GreenSock is an open source tool with GitHub stars and GitHub forks. Here’s a link to GreenSock's open source repository on GitHub

Top Alternatives to GreenSock

  • CreateJS
    CreateJS

    It is a suite of modular libraries and tools which work together or independently to enable rich interactive content on open web technologies via HTML5. These libraries are interoperable with all modern desktop and mobile browsers, and have been thoroughly tested to achieve performance and reliability in the widest range of browsers possible. ...

  • BabylonJS
    BabylonJS

    A complete JavaScript framework for building 3D games with HTML5, WebGL, WebVR and Web Audio. ...

  • anime.js
    anime.js

    It is a lightweight JavaScript animation library with a simple, yet powerful API. It works with CSS properties, SVG, DOM attributes and JavaScript Objects. ...

  • Lottie
    Lottie

    Lottie is a mobile library for Android and iOS that parses Adobe After Effects animations exported as json with Bodymovin and renders them natively on mobile! ...

  • three.js
    three.js

    It is a cross-browser JavaScript library and Application Programming Interface used to create and display animated 3D computer graphics in a web browser. ...

  • D3.js
    D3.js

    It is a JavaScript library for manipulating documents based on data. Emphasises on web standards gives you the full capabilities of modern browsers without tying yourself to a proprietary framework. ...

  • jQuery
    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

GreenSock alternatives & related posts

CreateJS logo

CreateJS

12
35
0
A javascript suite of open source libraries and tools
12
35
+ 1
0
PROS OF CREATEJS
    Be the first to leave a pro
    CONS OF CREATEJS
      Be the first to leave a con

      related CreateJS posts

      BabylonJS logo

      BabylonJS

      44
      98
      0
      A real time 3D engine
      44
      98
      + 1
      0
      PROS OF BABYLONJS
        Be the first to leave a pro
        CONS OF BABYLONJS
          Be the first to leave a con

          related BabylonJS posts

          Shared insights
          on
          BabylonJSBabylonJSthree.jsthree.jsUnityUnity

          We already have an existing 3d interactive application for windows, mac, and iOS devices and have planned to move that app to the web for high availability to different types of users. I have been searching for different options for it. Our existing application is made in Unity so we prefer to work on unity webgl but it also has its drawbacks. Other than that we are also thinking to change the tech stack to three.js or BabylonJS due to their high compatibility with the web ecosystem. I want to know which engine/library/framework we should use for the development of our 3d web application. Also with unity webgl, we want to develop all UI parts in web technologies only and will use the unity3d for 3d part only.

          Points that are very important to consider - 1. Memory optimization and allocation 2. Quality 3. Shaders 4. Materials 5. Lighting 6. Mesh editing, mesh creation at runtime 7. Ar 8. Vr 10. Support on different browsers including mobile browsers 11. Physics(gravity, collision, cloth simulation, etc.) 12. Initial load time 13. Speed and performance 14. Max vertices count. What happens when we load models exceeding max vertex count? 15. Development time 16. Learning curve (Unity3d we already working on) 17. Ease of use. What artists can do using any platform eg. in unity3d, artists can edit materials, set up lighting etc? 18. Future scope 19. Scalability 20. Integration with web ecosystem

          See more
          anime.js logo

          anime.js

          39
          52
          0
          A lightweight JavaScript animation library
          39
          52
          + 1
          0
          PROS OF ANIME.JS
            Be the first to leave a pro
            CONS OF ANIME.JS
              Be the first to leave a con

              related anime.js posts

              Lottie logo

              Lottie

              283
              297
              4
              Easily add high-quality animation to any native app (by Airbnb)
              283
              297
              + 1
              4
              PROS OF LOTTIE
              • 2
                Is free
              • 1
                Multi platform
              • 1
                Open source
              CONS OF LOTTIE
                Be the first to leave a con

                related Lottie posts

                three.js logo

                three.js

                498
                387
                0
                A JavaScript 3D library
                498
                387
                + 1
                0
                PROS OF THREE.JS
                  Be the first to leave a pro
                  CONS OF THREE.JS
                    Be the first to leave a con

                    related three.js posts

                    Shared insights
                    on
                    BabylonJSBabylonJSthree.jsthree.jsUnityUnity

                    We already have an existing 3d interactive application for windows, mac, and iOS devices and have planned to move that app to the web for high availability to different types of users. I have been searching for different options for it. Our existing application is made in Unity so we prefer to work on unity webgl but it also has its drawbacks. Other than that we are also thinking to change the tech stack to three.js or BabylonJS due to their high compatibility with the web ecosystem. I want to know which engine/library/framework we should use for the development of our 3d web application. Also with unity webgl, we want to develop all UI parts in web technologies only and will use the unity3d for 3d part only.

                    Points that are very important to consider - 1. Memory optimization and allocation 2. Quality 3. Shaders 4. Materials 5. Lighting 6. Mesh editing, mesh creation at runtime 7. Ar 8. Vr 10. Support on different browsers including mobile browsers 11. Physics(gravity, collision, cloth simulation, etc.) 12. Initial load time 13. Speed and performance 14. Max vertices count. What happens when we load models exceeding max vertex count? 15. Development time 16. Learning curve (Unity3d we already working on) 17. Ease of use. What artists can do using any platform eg. in unity3d, artists can edit materials, set up lighting etc? 18. Future scope 19. Scalability 20. Integration with web ecosystem

                    See more
                    Shared insights
                    on
                    WebGLWebGLthree.jsthree.js

                    I want a advice on what to use as a beginner three.js or WebGL?

                    See more
                    D3.js logo

                    D3.js

                    1.7K
                    1.6K
                    634
                    A JavaScript visualization library for HTML and SVG
                    1.7K
                    1.6K
                    + 1
                    634
                    PROS OF D3.JS
                    • 187
                      Beautiful visualizations
                    • 98
                      Svg
                    • 91
                      Data-driven
                    • 80
                      Large set of examples
                    • 60
                      Data-driven documents
                    • 23
                      Visualization components
                    • 20
                      Transitions
                    • 18
                      Dynamic properties
                    • 16
                      Plugins
                    • 11
                      Transformation
                    • 7
                      Makes data interactive
                    • 4
                      Components
                    • 4
                      Enter and Exit
                    • 3
                      Exhaustive
                    • 3
                      Open Source
                    • 3
                      Backed by the new york times
                    • 2
                      Easy and beautiful
                    • 1
                      Awesome Community Support
                    • 1
                      Simple elegance
                    • 1
                      Templates, force template
                    • 1
                      Angular 4
                    CONS OF D3.JS
                    • 10
                      Beginners cant understand at all
                    • 5
                      Complex syntax

                    related D3.js posts

                    Tim Abbott
                    Shared insights
                    on
                    Plotly.jsPlotly.jsD3.jsD3.js
                    at

                    We use Plotly (just their open source stuff) for Zulip's user-facing and admin-facing statistics graphs because it's a reasonably well-designed JavaScript graphing library.

                    If you've tried using D3.js, it's a pretty poor developer experience, and that translates to spending a bunch of time getting the graphs one wants even for things that are conceptually pretty basic. Plotly isn't amazing (it's decent), but it's way better than than D3 unless you have very specialized needs.

                    See more

                    I'm a student, and I have a project to build an application (Visual analytics tool) that takes a Microsoft Excel file, cleans the data, and visualizes it. Also, the app should allow the user to filter and interact with it.

                    1- should I make it desktop application or web application? : I'm leaning toward (desktop)

                    2- D3.js OR Python?

                    3- better excel or CSV?

                    I'm a beginner Inspiration for interaction and look of the app: eventflow application.

                    See more
                    jQuery logo

                    jQuery

                    176.1K
                    55.9K
                    6.6K
                    The Write Less, Do More, JavaScript Library.
                    176.1K
                    55.9K
                    + 1
                    6.6K
                    PROS OF JQUERY
                    • 1.3K
                      Cross-browser
                    • 957
                      Dom manipulation
                    • 807
                      Power
                    • 660
                      Open source
                    • 610
                      Plugins
                    • 458
                      Easy
                    • 395
                      Popular
                    • 350
                      Feature-rich
                    • 281
                      Html5
                    • 227
                      Light weight
                    • 92
                      Simple
                    • 84
                      Great community
                    • 79
                      CSS3 Compliant
                    • 69
                      Mobile friendly
                    • 67
                      Fast
                    • 43
                      Intuitive
                    • 42
                      Swiss Army knife for webdev
                    • 35
                      Huge Community
                    • 11
                      Easy to learn
                    • 4
                      Clean code
                    • 3
                      Because of Ajax request :)
                    • 2
                      Just awesome
                    • 2
                      Used everywhere
                    • 2
                      Powerful
                    • 2
                      Nice
                    • 1
                      Widely Used
                    • 1
                      Improves productivity
                    • 1
                      Open Source, Simple, Easy Setup
                    • 1
                      It Just Works
                    • 1
                      Industry acceptance
                    • 1
                      Allows great manipulation of HTML and CSS
                    • 1
                      Javascript
                    • 1
                      Easy Setup
                    CONS OF JQUERY
                    • 6
                      Large size
                    • 5
                      Sometimes inconsistent API
                    • 5
                      Encourages DOM as primary data source
                    • 2
                      Live events is overly complex feature

                    related jQuery posts

                    Kir Shatrov
                    Engineering Lead at Shopify · | 21 upvotes · 695.8K views

                    The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

                    Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

                    #FrameworksFullStack #Languages

                    See more
                    Ganesa Vijayakumar
                    Full Stack Coder | Technical Lead · | 19 upvotes · 2.8M views

                    I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

                    I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

                    As per my work experience and knowledge, I have chosen the followings stacks to this mission.

                    UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

                    Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

                    Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

                    Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

                    Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

                    Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

                    Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

                    Happy Coding! Suggestions are welcome! :)

                    Thanks, Ganesa

                    See more
                    React logo

                    React

                    131.8K
                    108K
                    3.9K
                    A JavaScript library for building user interfaces
                    131.8K
                    108K
                    + 1
                    3.9K
                    PROS OF REACT
                    • 777
                      Components
                    • 660
                      Virtual dom
                    • 569
                      Performance
                    • 494
                      Simplicity
                    • 439
                      Composable
                    • 177
                      Data flow
                    • 162
                      Declarative
                    • 124
                      Isn't an mvc framework
                    • 114
                      Reactive updates
                    • 112
                      Explicit app state
                    • 40
                      JSX
                    • 25
                      Learn once, write everywhere
                    • 19
                      Uni-directional data flow
                    • 18
                      Easy to Use
                    • 14
                      Works great with Flux Architecture
                    • 10
                      Great perfomance
                    • 8
                      Built by Facebook
                    • 7
                      Javascript
                    • 5
                      Speed
                    • 5
                      TypeScript support
                    • 4
                      Feels like the 90s
                    • 4
                      Hooks
                    • 4
                      Awesome
                    • 4
                      Easy to start
                    • 4
                      Scalable
                    • 3
                      Props
                    • 3
                      Excellent Documentation
                    • 3
                      Scales super well
                    • 3
                      Cross-platform
                    • 3
                      Server Side Rendering
                    • 3
                      Fancy third party tools
                    • 3
                      Server side views
                    • 3
                      Functional
                    • 2
                      Very gentle learning curve
                    • 2
                      Simple
                    • 2
                      Closer to standard JavaScript and HTML than others
                    • 2
                      Super easy
                    • 2
                      Rich ecosystem
                    • 2
                      Allows creating single page applications
                    • 2
                      Fast evolving
                    • 2
                      Simple, easy to reason about and makes you productive
                    • 2
                      Start simple
                    • 2
                      Just the View of MVC
                    • 2
                      Beautiful and Neat Component Management
                    • 2
                      Sdfsdfsdf
                    • 2
                      Has functional components
                    • 2
                      Has arrow functions
                    • 2
                      Strong Community
                    • 2
                      Great migration pathway for older systems
                    • 2
                      SSR
                    • 1
                      Fragments
                    • 1
                      Every decision architecture wise makes sense
                    • 1
                      Split your UI into components with one true state
                    • 1
                      Sharable
                    • 1
                      Permissively-licensed
                    • 0
                      Image upload
                    • 0
                      Recharts
                    CONS OF REACT
                    • 36
                      Requires discipline to keep architecture organized
                    • 24
                      No predefined way to structure your app
                    • 23
                      Need to be familiar with lots of third party packages
                    • 9
                      JSX
                    • 7
                      Not enterprise friendly
                    • 5
                      One-way binding only
                    • 2
                      State consistency with backend neglected
                    • 2
                      Bad Documentation
                    • 1
                      Paradigms change too fast

                    related React posts

                    Vaibhav Taunk
                    Team Lead at Technovert · | 31 upvotes · 1.9M views

                    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

                    See more
                    Adebayo Akinlaja
                    Engineering Manager at Andela · | 27 upvotes · 1.1M views

                    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

                    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

                    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

                    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

                    See more