Alternatives to jQuery logo

Alternatives to jQuery

Bootstrap, JavaScript, React, AngularJS, and jQuery Mobile are the most popular alternatives and competitors to jQuery.
166.9K
48.6K
+ 1
6.5K

What is jQuery and what are its top alternatives?

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.
jQuery is a tool in the Javascript UI Libraries category of a tech stack.
jQuery is an open source tool with 55.5K GitHub stars and 20.1K GitHub forks. Here’s a link to jQuery's open source repository on GitHub

Top Alternatives to jQuery

  • Bootstrap

    Bootstrap

    Bootstrap is the most popular HTML, CSS, and JS framework for developing responsive, mobile first projects on the web. ...

  • JavaScript

    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • 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. ...

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • jQuery Mobile

    jQuery Mobile

    jQuery Mobile is a HTML5-based user interface system designed to make responsive web sites and apps that are accessible on all smartphone, tablet and desktop devices. ...

  • 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. ...

  • Zepto

    Zepto

    While 100% jQuery coverage is not a design goal, the APIs provided match their jQuery counterparts. The goal is to have a ~5-10k modular library that downloads and executes fast, with a familiar and versatile API, so you can concentrate on getting stuff done. ...

  • Lodash

    Lodash

    A JavaScript utility library delivering consistency, modularity, performance, & extras. It provides utility functions for common programming tasks using the functional programming paradigm. ...

jQuery alternatives & related posts

Bootstrap logo

Bootstrap

52.8K
11.7K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52.8K
11.7K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 943
    Consistent
  • 777
    Great docs
  • 677
    Flexible
  • 466
    HTML, CSS, and JS framework
  • 411
    Open source
  • 375
    Widely used
  • 368
    Customizable
  • 241
    HTML framework
  • 76
    Popular
  • 75
    Easy setup
  • 75
    Mobile first
  • 56
    Great grid system
  • 49
    Great community
  • 38
    Future compatibility
  • 34
    Integration
  • 27
    Very powerful foundational front-end framework
  • 24
    Standard
  • 23
    Javascript plugins
  • 19
    Build faster prototypes
  • 18
    Preprocessors
  • 13
    Grids
  • 8
    Clean
  • 7
    Good for a person who hates CSS
  • 4
    Easy to setup and learn
  • 4
    Love it
  • 4
    Rapid development
  • 3
    Great and easy to use
  • 2
    Provide angular wrapper
  • 2
    Easy to use
  • 2
    Community
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Popularity
  • 2
    Great customer support
  • 2
    Clean and quick frontend development
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Great and easy
  • 1
    Material-ui
  • 1
    Reactjs
  • 1
    Geo
  • 1
    Boostrap
  • 1
    Pre-Defined components
  • 1
    Not tied to jQuery
  • 1
    Responsive design
  • 1
    Design Agnostic
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 1
    Painless front end development
  • 1
    So clean and simple
  • 1
    Numerous components
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 16
    Every site uses the defaults
  • 14
    Too much heavy decoration in default look
  • 14
    Grid system break points aren't ideal
  • 8
    Verbose styles
  • 1
    Super heavy

related Bootstrap posts

Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 19 upvotes · 2.4M 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
Francisco Quintero
Tech Lead at Dev As Pros · | 13 upvotes · 763.2K views

For Etom, a side project. We wanted to test an idea for a future and bigger project.

What Etom does is searching places. Right now, it leverages the Google Maps API. For that, we found a React component that makes this integration easy because using Google Maps API is not possible via normal API requests.

You kind of need a map to work as a proxy between the software and Google Maps API.

We hate configuration(coming from Rails world) so also decided to use Create React App because setting up a React app, with all the toys, it's a hard job.

Thanks to all the people behind Create React App it's easier to start any React application.

We also chose a module called Reactstrap which is Bootstrap UI in React components.

An important thing in this side project(and in the bigger project plan) is to measure visitor through out the app. For that we researched and found that Keen was a good choice(very good free tier limits) and also it is very simple to setup and real simple to send data to

Slack and Trello are our defaults tools to comunicate ideas and discuss topics, so, no brainer using them as well for this project.

See more
JavaScript logo

JavaScript

217.2K
167.3K
7.8K
Lightweight, interpreted, object-oriented language with first-class functions
217.2K
167.3K
+ 1
7.8K
PROS OF JAVASCRIPT
  • 1.6K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.1K
    Lots of great frameworks
  • 886
    Fast
  • 735
    Light weight
  • 415
    Flexible
  • 382
    You can't get a device today that doesn't run js
  • 282
    Non-blocking i/o
  • 232
    Ubiquitousness
  • 187
    Expressive
  • 50
    Extended functionality to web pages
  • 43
    Relatively easy language
  • 41
    Executed on the client side
  • 25
    Relatively fast to the end user
  • 21
    Pure Javascript
  • 16
    Functional programming
  • 11
    Async
  • 8
    Setup is easy
  • 7
    Full-stack
  • 7
    JavaScript is the New PHP
  • 7
    Its everywhere
  • 7
    Like it or not, JS is part of the web standard
  • 7
    Because I love functions
  • 6
    Expansive community
  • 6
    Can be used in backend, frontend and DB
  • 6
    Future Language of The Web
  • 5
    Popularized Class-Less Architecture & Lambdas
  • 5
    Everyone use it
  • 5
    Love-hate relationship
  • 5
    Easy to hire developers
  • 5
    Evolution of C
  • 5
    Supports lambdas and closures
  • 5
    Agile, packages simple to use
  • 5
    For the good parts
  • 4
    Scope manipulation
  • 4
    It's fun
  • 4
    Client processing
  • 4
    Nice
  • 4
    Easy to make something
  • 4
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 4
    Easy
  • 4
    Photoshop has 3 JS runtimes built in
  • 4
    Can be used both as frontend and backend as well
  • 4
    Most Popular Language in the World
  • 4
    No need to use PHP
  • 4
    Everywhere
  • 4
    Hard not to use
  • 4
    Promise relationship
  • 4
    Stockholm Syndrome
  • 4
    1.6K Can be used on frontend/backend
  • 4
    Client side JS uses the visitors CPU to save Server Res
  • 4
    It let's me use Babel & Typescript
  • 4
    Its fun and fast
  • 4
    Powerful
  • 4
    Versitile
  • 4
    What to add
  • 4
    Clojurescript
  • 4
    Function expressions are useful for callbacks
  • 3
    Because it is so simple and lightweight
  • 3
    Only Programming language on browser
  • 2
    JavaScript j.s
  • 2
    Acoperișul 0757604335
CONS OF JAVASCRIPT
  • 21
    A constant moving target, too much churn
  • 20
    Horribly inconsistent
  • 14
    Javascript is the New PHP
  • 8
    No ability to monitor memory utilitization
  • 6
    Shows Zero output in case of ANY error
  • 5
    Can be ugly
  • 4
    Thinks strange results are better than errors
  • 2
    No GitHub
  • 1
    Slow

related JavaScript posts

Zach Holman

Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 4.1M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.6M 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 · | 26 upvotes · 724.7K 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
AngularJS logo

AngularJS

44.6K
32K
5.3K
Superheroic JavaScript MVW Framework
44.6K
32K
+ 1
5.3K
PROS OF ANGULARJS
  • 886
    Quick to develop
  • 586
    Great mvc
  • 570
    Powerful
  • 520
    Restful
  • 503
    Backed by google
  • 348
    Two-way data binding
  • 343
    Javascript
  • 327
    Open source
  • 305
    Dependency injection
  • 197
    Readable
  • 76
    Fast
  • 64
    Great community
  • 64
    Directives
  • 56
    Free
  • 39
    Extend html vocabulary
  • 30
    Components
  • 26
    Easy to test
  • 25
    Easy to learn
  • 24
    Easy to templates
  • 24
    Great documentation
  • 22
    Easy to start
  • 18
    Light weight
  • 18
    Awesome
  • 15
    Angular 2.0
  • 15
    Javascript mvw framework
  • 14
    Great extensions
  • 14
    Efficient
  • 11
    Easy to prototype with
  • 9
    High performance
  • 9
    Coffeescript
  • 8
    Two-way binding
  • 8
    Lots of community modules
  • 8
    Mvc
  • 7
    Clean and keeps code readable
  • 7
    Easy to e2e
  • 6
    Easy for small applications
  • 6
    One of the best frameworks
  • 5
    Works great with jquery
  • 5
    Fast development
  • 3
    Hierarchical Data Structure
  • 3
    Be a developer, not a plumber.
  • 3
    Dart
  • 3
    I do not touch DOM
  • 3
    Declarative programming
  • 3
    Typescript
  • 3
    Community
  • 3
    The two-way Data Binding is awesome
  • 2
    The powerful of binding, routing and controlling routes
  • 2
    Fkin awesome
  • 2
    Opinionated in the right areas
  • 2
    Supports api , easy development
  • 2
    Common Place
  • 2
    Amazing community support
  • 2
    Great
  • 2
    Very very useful and fast framework for development
  • 2
    Readable code
  • 2
    Programming fun again
  • 2
    Linear learning curve
  • 2
    Scopes
  • 1
    Acoperișul 0757604335
  • 1
    Js
  • 1
    Google.com
  • 1
    Angular js
  • 1
    Httpș//Acoperișul 0757604335
  • 1
    Shvzjn
  • 1
    Bot Ionescu
CONS OF ANGULARJS
  • 10
    Complex
  • 3
    Dependency injection
  • 2
    Learning Curve
  • 2
    Event Listener Overload
  • 1
    Hard to learn

related AngularJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 19 upvotes · 727.7K views

Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

  • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
  • Vue Styleguidist as our style guide and pool of developed Vue.js components
  • Vuetify as Material Component Framework (for fast app development)
  • TypeScript as programming language
  • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
  • ESLint, TSLint and Prettier for coding style and code analyzes
  • Jest as testing framework
  • Google Fonts and Font Awesome for typography and icon toolkit
  • NativeScript-Vue for mobile development

The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

  • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
  • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
  • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
  • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
  • Large scaling. Vue.js can help to develop pretty large reusable templates.
  • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
See more
jQuery Mobile logo

jQuery Mobile

1.4K
292
0
Touch-Optimized Web Framework for Smartphones & Tablets
1.4K
292
+ 1
0
PROS OF JQUERY MOBILE
    Be the first to leave a pro
    CONS OF JQUERY MOBILE
      Be the first to leave a con

      related jQuery Mobile posts

      Ganesa Vijayakumar
      Full Stack Coder | Module Lead · | 19 upvotes · 2.4M 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
      D3.js logo

      D3.js

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

      related D3.js posts

      Tim Abbott
      Shared insights
      on
      Plotly.js
      D3.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
      Zepto logo

      Zepto

      293
      67
      3
      Minimalist JavaScript library for modern browsers, with a jQuery-compatible API
      293
      67
      + 1
      3
      PROS OF ZEPTO
      • 3
        Lightweight
      CONS OF ZEPTO
        Be the first to leave a con

        related Zepto posts

        Lodash logo

        Lodash

        5K
        805
        2
        A JavaScript utility library
        5K
        805
        + 1
        2
        PROS OF LODASH
        • 2
          Better than Underscore
        • 0
          Better that Underscore
        CONS OF LODASH
        • 1
          It reduce the performance

        related Lodash posts

        Elemental UI Vue.js vuex Node.js ES6 ESLint lodash Webpack Yarn Git

        See more