Alternatives to Vue.js logo

Alternatives to Vue.js

React, jQuery, Bootstrap, Angular 2, and AngularJS are the most popular alternatives and competitors to Vue.js.
32.8K
25.4K
+ 1
1.3K

What is Vue.js and what are its top alternatives?

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.
Vue.js is a tool in the Javascript UI Libraries category of a tech stack.
Vue.js is an open source tool with 183.2K GitHub stars and 29K GitHub forks. Here’s a link to Vue.js's open source repository on GitHub

Top Alternatives to Vue.js

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

  • jQuery

    jQuery

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

  • Bootstrap

    Bootstrap

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

  • Angular 2

    Angular 2

    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...

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

  • Svelte

    Svelte

    If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads. ...

  • jQuery UI

    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

  • Backbone.js

    Backbone.js

    Backbone supplies structure to JavaScript-heavy applications by providing models key-value binding and custom events, collections with a rich API of enumerable functions, views with declarative event handling, and connects it all to your existing application over a RESTful JSON interface. ...

Vue.js alternatives & related posts

React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.4M 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
Johnny Bell
Software Engineer at Weedmaps · | 26 upvotes · 346.5K views
Shared insights
on
Vue.js
React

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
jQuery logo

jQuery

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

related jQuery posts

Kir Shatrov
Engineering Lead at Shopify · | 20 upvotes · 461.6K 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 | Module Lead · | 18 upvotes · 2.2M 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
Bootstrap logo

Bootstrap

52.1K
11.3K
7.6K
Simple and flexible HTML, CSS, and JS for popular UI components and interactions
52.1K
11.3K
+ 1
7.6K
PROS OF BOOTSTRAP
  • 1.6K
    Responsiveness
  • 1.2K
    UI components
  • 945
    Consistent
  • 776
    Great docs
  • 677
    Flexible
  • 466
    HTML, CSS, and JS framework
  • 410
    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
    Love it
  • 4
    Easy to setup and learn
  • 4
    Rapid development
  • 2
    Clean and quick frontend development
  • 2
    Provide angular wrapper
  • 2
    Great and easy to use
  • 2
    Great and easy
  • 2
    Powerful grid system, Rapid development, Customization
  • 2
    Community
  • 2
    Great customer support
  • 2
    Popularity
  • 2
    Great and easy to make a responsive website
  • 2
    Sprzedam opla
  • 2
    Easy to use
  • 1
    Painless front end development
  • 1
    Responsive design
  • 1
    Reactjs
  • 1
    Geo
  • 1
    Design Agnostic
  • 1
    So clean and simple
  • 1
    Numerous components
  • 1
    Recognizable
  • 1
    Intuitive
  • 1
    Love the classes?
  • 1
    Material-ui
  • 1
    Pre-Defined components
  • 1
    Boostrap
  • 1
    It's fast
  • 1
    Felxible, comfortable, user-friendly
  • 1
    The fame
  • 1
    Easy setup2
  • 0
    Frefsd
CONS OF BOOTSTRAP
  • 25
    Javascript is tied to jquery
  • 15
    Every site uses the defaults
  • 13
    Too much heavy decoration in default look
  • 13
    Grid system break points aren't ideal
  • 8
    Verbose styles

related Bootstrap posts

Hello, I hope everyone is doing good and safe. I need advice on what to learn more, I have started learning HTML, CSS, Bootstrap, JavaScript, Node.js, ExpressJS, React. eventually will learn MongoDB too. I would like to be a Front End developer or full-stack developer. What else would be the suggestion to get a job and what things I need to focus more on as a fresher to make my skills better. Do I have to be good in Algorithms and Dynamic Programming to find a job for entry-level? Looking forward to hearing from you guys for suggestions. 

See more
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 18 upvotes · 2.2M 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
Angular 2 logo

Angular 2

4.4K
3.4K
407
A platform for building mobile and desktop web applications
4.4K
3.4K
+ 1
407
PROS OF ANGULAR 2
  • 92
    It's a powerful framework
  • 47
    Straight-forward architecture
  • 39
    Great UI and Business Logic separation
  • 37
    TypeScript
  • 37
    Powerful, maintainable, fast
  • 33
    Amazing CLI
  • 30
    Great mvc
  • 22
    Powerfull Dependency Injection
  • 17
    Easy to build
  • 12
    Opinionated, batteries-included approach
  • 9
    All in one Framework
  • 7
    Solid Standard Setup.
  • 7
    Schematics
  • 6
    Structured
  • 5
    Performance
  • 3
    Only for single page applications
  • 3
    Complex
  • 1
    Builders
  • 0
    React
CONS OF ANGULAR 2
  • 7
    Overcomplicated
  • 7
    Large overhead in file size and initialization time
  • 2
    CLI not open to other test and linting tools
  • 1
    Cringe
  • 1
    Ugly code

related Angular 2 posts

When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

  1. Many in our community are already using React internally and will be able to contribute.
  2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

See more
Max Musing
Founder & CEO at BaseDash · | 10 upvotes · 173.1K views

From my experience of the early startup world, a majority of companies these days use Node.js. Python and Go are the next biggest languages, but significantly smaller than Node.

However, if you're having trouble with the front end aspect of Django, using Node probably won't make that easier for you. You'll have a lot more options between front end frameworks (React, Vue.js, Angular 2) , but they'll definitely take more time to learn than Django's templating system.

Think about whether you want to focus on front end or back end for now, and make a decision from there.

See more
AngularJS logo

AngularJS

41.4K
29.2K
5.3K
Superheroic JavaScript MVW Framework
41.4K
29.2K
+ 1
5.3K
PROS OF ANGULARJS
  • 886
    Quick to develop
  • 587
    Great mvc
  • 571
    Powerful
  • 522
    Restful
  • 504
    Backed by google
  • 349
    Two-way data binding
  • 344
    Javascript
  • 328
    Open source
  • 306
    Dependency injection
  • 198
    Readable
  • 76
    Fast
  • 65
    Directives
  • 64
    Great community
  • 57
    Free
  • 39
    Extend html vocabulary
  • 30
    Components
  • 26
    Easy to test
  • 25
    Easy to learn
  • 24
    Great documentation
  • 24
    Easy to templates
  • 22
    Easy to start
  • 18
    Awesome
  • 18
    Light weight
  • 15
    Angular 2.0
  • 15
    Javascript mvw framework
  • 14
    Efficient
  • 14
    Great extensions
  • 11
    Easy to prototype with
  • 9
    High performance
  • 9
    Coffeescript
  • 8
    Mvc
  • 8
    Two-way binding
  • 8
    Lots of community modules
  • 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
    I do not touch DOM
  • 3
    Be a developer, not a plumber.
  • 3
    Dart
  • 3
    Hierarchical Data Structure
  • 3
    The two-way Data Binding is awesome
  • 3
    Community
  • 3
    Typescript
  • 3
    Declarative programming
  • 2
    The powerful of binding, routing and controlling routes
  • 2
    Fkin awesome
  • 2
    Scopes
  • 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
  • 1
    Bot Ionescu
  • 1
    Acoperișul 0757604335
  • 1
    Js
  • 1
    Google.com
  • 1
    Angular js
  • 1
    Shvzjn
  • 1
    Httpș//Acoperișul 0757604335
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 · | 24 upvotes · 1.6M 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 · 545.1K 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
Svelte logo

Svelte

535
646
349
A UI framework that compiles into tiny standalone JavaScript modules
535
646
+ 1
349
PROS OF SVELTE
  • 34
    Performance
  • 28
    Reactivity
  • 27
    Javascript compiler (do that browsers don't have to)
  • 24
    Components
  • 22
    Lightweight
  • 22
    Real Reactivity
  • 21
    Simplicity
  • 20
    Fast as vanilajs
  • 18
    Near to no learning curve
  • 15
    Compiler based
  • 14
    All in one
  • 14
    Use existing js libraries
  • 13
    Scalable
  • 11
    Composable
  • 11
    Very easy for beginners
  • 11
    SSR
  • 9
    Ease of use
  • 9
    No runtime overhead
  • 8
    Built in store
  • 5
    Typescript
  • 4
    Start with pure html + css
  • 4
    Best Developer Experience
  • 4
    Templates
  • 1
    Speed
CONS OF SVELTE
  • 2
    Complex
  • 2
    Learning Curve
  • 2
    Hard to learn
  • 2
    Event Listener Overload
  • 1
    Little to no libraries

related Svelte posts

Sarmad Chaudhary
Founder & CEO at Ebiz Ltd. · | 9 upvotes · 350K views

Hi there!

I just want to have a simple poll/vote...

If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

Your advice would help a lot! Thanks in advance :)

See more
jQuery UI logo

jQuery UI

35K
8.5K
895
Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
35K
8.5K
+ 1
895
PROS OF JQUERY UI
  • 213
    Ui components
  • 155
    Cross-browser
  • 121
    Easy
  • 100
    It's jquery
  • 81
    Open source
  • 57
    Widgets
  • 48
    Plugins
  • 46
    Popular
  • 39
    Datepicker
  • 23
    Great community
  • 7
    DOM Manipulation
  • 5
    Themes
  • 0
    Some good ui components
CONS OF JQUERY UI
    Be the first to leave a con

    related jQuery UI posts

    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 18 upvotes · 2.2M 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
    Khauth György
    CTO at SalesAutopilot Kft. · | 12 upvotes · 355.5K views

    I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

    Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

    On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

    On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

    See more
    Backbone.js logo

    Backbone.js

    6K
    2.3K
    678
    Give your JS App some Backbone with Models, Views, Collections, and Events
    6K
    2.3K
    + 1
    678
    PROS OF BACKBONE.JS
    • 136
      Javascript structure
    • 102
      Models
    • 98
      Simple
    • 77
      Restful
    • 59
      Easy api
    • 46
      Flexible
    • 45
      Open source
    • 44
      Fast to pick up
    • 34
      Events
    • 25
      JSON
    • 8
      OOP
    • 2
      Lightweight
    • 1
      Easy customizable
    • 1
      Collections
    CONS OF BACKBONE.JS
    • 1
      Requires underscore.js

    related Backbone.js posts

    Dan Robinson

    The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

    Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

    #JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

    See more
    Marcos Iglesias
    Sr. Software Engineer at Eventbrite · | 13 upvotes · 143.3K views

    We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.

    But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.

    With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.

    See more