Alternatives to Angular 2 logo

Alternatives to Angular 2

React, Polymer, Aurelia, Vue.js, and Meteor are the most popular alternatives and competitors to Angular 2.
4.9K
3.9K
+ 1
453

What is Angular 2 and what are its top alternatives?

It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications.
Angular 2 is a tool in the Javascript MVC Frameworks category of a tech stack.
Angular 2 is an open source tool with 81.5K GitHub stars and 21.5K GitHub forks. Here’s a link to Angular 2's open source repository on GitHub

Top Alternatives to Angular 2

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

  • Polymer
    Polymer

    Polymer is a new type of library for the web, designed to leverage the existing browser infrastructure to provide the encapsulation and extendability currently only available in JS libraries. Polymer is based on a set of future technologies, including Shadow DOM, Custom Elements and Model Driven Views. Currently these technologies are implemented as polyfills or shims, but as browsers adopt these features natively, the platform code that drives Polymer evacipates, leaving only the value-adds. ...

  • Aurelia
    Aurelia

    Aurelia is a next generation JavaScript client framework that leverages simple conventions to empower your creativity. ...

  • Vue.js
    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • Meteor
    Meteor

    A Meteor application is a mix of JavaScript that runs inside a client web browser, JavaScript that runs on the Meteor server inside a Node.js container, and all the supporting HTML fragments, CSS rules, and static assets. ...

  • Knockout
    Knockout

    It is a JavaScript library that helps you to create rich, responsive display and editor user interfaces with a clean underlying data model. Any time you have sections of UI that update dynamically (e.g., changing depending on the user’s actions or when an external data source changes), it can help you implement it more simply and maintainably. ...

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

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

Angular 2 alternatives & related posts

React logo

React

129K
105.1K
3.9K
A JavaScript library for building user interfaces
129K
105.1K
+ 1
3.9K
PROS OF REACT
  • 775
    Components
  • 658
    Virtual dom
  • 567
    Performance
  • 492
    Simplicity
  • 438
    Composable
  • 176
    Data flow
  • 162
    Declarative
  • 124
    Isn't an mvc framework
  • 114
    Reactive updates
  • 111
    Explicit app state
  • 40
    JSX
  • 24
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 17
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    Speed
  • 5
    TypeScript support
  • 4
    Easy to start
  • 4
    Scalable
  • 4
    Awesome
  • 4
    Feels like the 90s
  • 4
    Hooks
  • 3
    Excellent Documentation
  • 3
    Scales super well
  • 3
    Functional
  • 3
    Obama
  • 3
    Fancy third party tools
  • 3
    Server side views
  • 3
    Props
  • 3
    Server Side Rendering
  • 3
    Cross-platform
  • 2
    Rich ecosystem
  • 2
    Start simple
  • 2
    Allows creating single page applications
  • 2
    Sdfsdfsdf
  • 2
    Beautiful and Neat Component Management
  • 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
    Just the View of MVC
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Split your UI into components with one true state
  • 1
    Fragments
  • 0
    Recharts
CONS OF REACT
  • 36
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 22
    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
Polymer logo

Polymer

424
449
121
A new library built on top of Web Components, designed to leverage the evolving web platform on modern...
424
449
+ 1
121
PROS OF POLYMER
  • 51
    Web components
  • 30
    Material design
  • 14
    HTML
  • 13
    Components
  • 5
    Open source
  • 4
    It uses the platform
  • 3
    Designer friendly. HTMLX concepts
  • 1
    Like the interesting naming convention for elements
CONS OF POLYMER
  • 1
    Last version is like 2 years ago? that's totally rad

related Polymer posts

Adam Rabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 6 upvotes · 115.6K views

At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

See more
Ido Shamun
at The Elegant Monkeys · | 6 upvotes · 84.7K views
Shared insights
on
Vue.jsVue.jsReactReactPolymerPolymer
at

For developing our #frontend applications, we decided to use Vue.js . Being such an easy to learn library, compared to React for example, it made everything so easy. At first we started with Polymer but the existing tooling and small community at the time made us look for alternatives.

See more
Aurelia logo

Aurelia

264
272
374
Next gen JS framework written with ES6 and ES7. Integrates with Web Components. No external dependencies except polyfills.
264
272
+ 1
374
PROS OF AURELIA
  • 47
    Simple with conventions
  • 42
    Modern architecture
  • 39
    Makes sense and is mostly javascript not framework
  • 31
    Extensible
  • 28
    Integrates well with other components
  • 27
    Easy to use
  • 25
    Dependency Injection
  • 22
    Modular
  • 20
    Great router
  • 16
    Adaptive Data Binding
  • 13
    Typescript, ES2015, ES2016
  • 11
    IoC, Modularity, Simplicity, Full Stack
  • 9
    Good binding system
  • 9
    Based on ES7
  • 6
    Testable
  • 6
    Convention based
  • 5
    Quick to develop
  • 4
    Solid Documentation
  • 4
    Evolving standards compliance
  • 4
    Smooth learning curve
  • 4
    Outstanding Support (paid)
  • 1
    Reactive binding system
  • 1
    TypeScript
CONS OF AURELIA
  • 4
    None

related Aurelia posts

Adam Rabinovitch
Global Technical Recruiting Lead & Engineering Evangelist at Beamery · | 6 upvotes · 115.6K views

At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn’t scale nicely. Features clash with each other. Isolation doesn’t come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

See more
Vue.js logo

Vue.js

43K
34.6K
1.5K
A progressive framework for building user interfaces
43K
34.6K
+ 1
1.5K
PROS OF VUE.JS
  • 287
    Simple and easy to start with
  • 222
    Good documentation
  • 189
    Components
  • 126
    Simple the best
  • 96
    Simplified AngularJS
  • 87
    Reactive
  • 72
    Intuitive APIs
  • 52
    Javascript
  • 48
    Changed my front end coding life
  • 45
    Configuration is smooth
  • 34
    Easy to learn
  • 32
    So much fun to use
  • 23
    Progressive
  • 19
    Virtual dom
  • 15
    Faster than bulldogs on hot tarmac
  • 10
    It's magic
  • 10
    Component is template, javascript and style in one
  • 8
    Best of Both Worlds
  • 8
    Perfomance
  • 7
    Without misleading licenses
  • 7
    Light Weight
  • 7
    Application structure
  • 7
    Elegant design
  • 6
    Intuitive and easy to use
  • 5
    Good command line interface
  • 4
    Like Angular only quicker to get started with
  • 4
    Single file components
  • 4
    Easy to integrate to HTML by inline-templates
  • 4
    Small learning curve
  • 4
    Logicless templates
  • 3
    Customer Render ending eg to HTML
  • 2
    Intuitive
  • 2
    Vuex
  • 2
    Lots of documentation
  • 2
    Component based
  • 2
    Bridge from Web Development to JS Development
  • 2
    Concise error messages
  • 2
    Supports several template languages
  • 2
    High performance
  • 2
    One-way data flow
  • 1
    GUI
  • 0
    React
CONS OF VUE.JS
  • 7
    Less Common Place
  • 3
    YXMLvsHTML Markup
  • 1
    Don't support fragments
  • 1
    Only support programatically multiple root nodes

related Vue.js posts

Johnny Bell
Shared insights
on
Vue.jsVue.jsReactReact

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
Shared insights
on
Vue.jsVue.jsReactReact

I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

See more
Meteor logo

Meteor

1.8K
1.7K
1.7K
An ultra-simple, database-everywhere, data-on-the-wire, pure-Javascript web framework
1.8K
1.7K
+ 1
1.7K
PROS OF METEOR
  • 252
    Real-time
  • 200
    Full stack, one language
  • 183
    Best app dev platform available today
  • 155
    Data synchronization
  • 152
    Javascript
  • 118
    Focus on your product not the plumbing
  • 107
    Hot code pushes
  • 106
    Open source
  • 102
    Live page updates
  • 92
    Latency compensation
  • 39
    Ultra-simple development environment
  • 29
    Real time awesome
  • 29
    Smart Packages
  • 23
    Great for beginners
  • 22
    Direct Cordova integration
  • 16
    Better than Rails
  • 15
    Less moving parts
  • 13
    It's just amazing
  • 10
    Blaze
  • 8
    Great community support
  • 8
    Plugins for everything
  • 6
    One command spits out android and ios ready apps.
  • 5
    0 to Production in no time
  • 5
    It just works
  • 4
    Coding Speed
  • 4
    Easy deployment
  • 4
    Is Agile in development hybrid(mobile/web)
  • 4
    You can grok it in a day. No ng nonsense
  • 2
    One Code => 3 Platforms: Web, Android and IOS
  • 2
    AngularJS Integration
  • 2
    Easy yet powerful
  • 2
    Community
  • 1
    Real time
  • 1
    Hookie friendly
  • 1
    High quality, very few bugs
  • 1
    Easy Setup
  • 1
    Free
  • 1
    Friendly to use
  • 1
    Stack available on Codeanywhere
  • 1
    Nosql
CONS OF METEOR
  • 4
    Hard to debug issues on the server-side
  • 4
    Heavily CPU bound
  • 4
    Does not scale well

related Meteor posts

Lucas Litton
Founder & CEO at Macombey · | 13 upvotes · 345.4K views

Next.js is probably the most enjoyable React framework our team could have picked. The development is an extremely smooth process, the file structure is beautiful and organized, and the speed is no joke. Our work with Next.js comes out much faster than if it was built on pure React or frameworks alike. We were previously developing all of our projects in Meteor before making the switch. We left Meteor due to the slow compiler and website speed. We deploy all of our Next.js projects on Vercel.

See more
Shared insights
on
MeteorMeteorNode.jsNode.js
at

Mixmax was originally built using Meteor as a single monolithic app. As more users began to onboard, we started noticing scaling issues, and so we broke out our first microservice: our Compose service, for writing emails and Sequences, was born as a Node.js service. Soon after that, we broke out all recipient searching and storage functionality to another Node.js microservice, our Contacts service. This practice of breaking out microservices in order to help our system more appropriately scale, by being more explicit about each microservice’s responsibilities, continued as we broke out numerous more microservices.

See more
Knockout logo

Knockout

252
190
5
Create rich, responsive UIs with JavaScript
252
190
+ 1
5
PROS OF KNOCKOUT
  • 2
    Data centered application
  • 2
    Great for validations
  • 1
    Open source
CONS OF KNOCKOUT
    Be the first to leave a con

    related Knockout posts

    AngularJS logo

    AngularJS

    49.4K
    36.1K
    5.2K
    Superheroic JavaScript MVW Framework
    49.4K
    36.1K
    + 1
    5.2K
    PROS OF ANGULARJS
    • 887
      Quick to develop
    • 587
      Great mvc
    • 572
      Powerful
    • 521
      Restful
    • 503
      Backed by google
    • 349
      Two-way data binding
    • 343
      Javascript
    • 328
      Open source
    • 305
      Dependency injection
    • 197
      Readable
    • 75
      Fast
    • 64
      Directives
    • 63
      Great community
    • 56
      Free
    • 38
      Extend html vocabulary
    • 29
      Components
    • 26
      Easy to test
    • 24
      Easy to learn
    • 23
      Easy to templates
    • 23
      Great documentation
    • 21
      Easy to start
    • 18
      Awesome
    • 17
      Light weight
    • 14
      Angular 2.0
    • 14
      Javascript mvw framework
    • 13
      Great extensions
    • 13
      Efficient
    • 10
      Easy to prototype with
    • 8
      High performance
    • 8
      Coffeescript
    • 7
      Mvc
    • 7
      Two-way binding
    • 7
      Lots of community modules
    • 6
      Easy to e2e
    • 6
      Clean and keeps code readable
    • 5
      Easy for small applications
    • 5
      One of the best frameworks
    • 4
      Fast development
    • 4
      Works great with jquery
    • 3
      I do not touch DOM
    • 2
      Be a developer, not a plumber.
    • 2
      Declarative programming
    • 2
      Dart
    • 2
      Community
    • 2
      The two-way Data Binding is awesome
    • 2
      Hierarchical Data Structure
    • 2
      Typescript
    • 1
      Botionescu@gmail.com
    • 1
      The powerful of binding, routing and controlling routes
    • 1
      Fkin awesome
    • 1
      Opinionated in the right areas
    • 1
      Supports api , easy development
    • 1
      Common Place
    • 1
      Great
    • 1
      Very very useful and fast framework for development
    • 1
      Amazing community support
    • 1
      Readable code
    • 1
      Linear learning curve
    • 1
      Scopes
    • 1
      Programming fun again
    • 1
      Acoperișul
    • 1
      Consistency with backend architecture if using Nest
    • 0
      Httpș//Acoperișul 0757604335
    • 0
      Angular js
    • 0
      Oautho loc
    • 0
      Shvzjn
    • 0
      Acoperișul 0757604335
    • 0
      Js
    • 0
      Bot Ionescu
    • 0
      Google.com
    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 · 2.5M 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 · | 22 upvotes · 1.2M 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
    Backbone.js logo

    Backbone.js

    6.7K
    2.9K
    678
    Give your JS App some Backbone with Models, Views, Collections, and Events
    6.7K
    2.9K
    + 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 · 172.7K 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