Alternatives to Ember.js logo

Alternatives to Ember.js

Vue.js, React, AngularJS, Backbone.js, and Angular 2 are the most popular alternatives and competitors to Ember.js.
1.2K
783
+ 1
765

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

A JavaScript framework that does all of the heavy lifting that you'd normally have to do by hand. There are tasks that are common to every web app; It does those things for you, so you can focus on building killer features and UI.
Ember.js is a tool in the Javascript MVC Frameworks category of a tech stack.
Ember.js is an open source tool with 22.1K GitHub stars and 4.3K GitHub forks. Here’s a link to Ember.js's open source repository on GitHub

Top Alternatives to Ember.js

  • Vue.js

    Vue.js

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

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

  • 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

    Angular 2

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

  • Aurelia

    Aurelia

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

  • Marionette

    Marionette

    It is a JavaScript library with a RESTful JSON interface and is based on the Model–view–presenter application design paradigm. Backbone is known for being lightweight, as its only hard dependency is on one JavaScript library, Underscore.js, plus jQuery for use of the full library. ...

  • JSF

    JSF

    It is used for building component-based user interfaces for web applications and was formalized as a standard through the Java Community ...

Ember.js alternatives & related posts

Vue.js logo

Vue.js

38.2K
30.4K
1.4K
A progressive framework for building user interfaces
38.2K
30.4K
+ 1
1.4K
PROS OF VUE.JS
  • 275
    Simple and easy to start with
  • 216
    Good documentation
  • 186
    Components
  • 123
    Simple the best
  • 95
    Simplified AngularJS
  • 81
    Reactive
  • 69
    Intuitive APIs
  • 48
    Javascript
  • 45
    Changed my front end coding life
  • 40
    Configuration is smooth
  • 28
    Easy to learn
  • 25
    So much fun to use
  • 20
    Progressive
  • 17
    Virtual dom
  • 13
    Faster than bulldogs on hot tarmac
  • 9
    It's magic
  • 8
    Best of Both Worlds
  • 8
    Component is template, javascript and style in one
  • 7
    Without misleading licenses
  • 7
    Perfomance
  • 7
    Application structure
  • 7
    Elegant design
  • 6
    Intuitive and easy to use
  • 5
    Light Weight
  • 4
    Easy to integrate to HTML by inline-templates
  • 4
    Good command line interface
  • 3
    Small learning curve
  • 3
    Like Angular only quicker to get started with
  • 3
    Customer Render ending eg to HTML
  • 2
    One-way data flow
  • 2
    Single file components
  • 2
    Intuitive
  • 2
    Lots of documentation
  • 2
    Component based
  • 2
    Bridge from Web Development to JS Development
  • 2
    Concise error messages
  • 2
    Logicless templates
  • 2
    Supports several template languages
  • 2
    High performance
  • 1
    GUI
CONS OF VUE.JS
  • 6
    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
React logo

React

112.7K
91.4K
3.8K
A JavaScript library for building user interfaces
112.7K
91.4K
+ 1
3.8K
PROS OF REACT
  • 760
    Components
  • 652
    Virtual dom
  • 563
    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
    Feels like the 90s
  • 4
    Scalable
  • 4
    Easy to start
  • 4
    Awesome
  • 3
    Fancy third party tools
  • 3
    Hooks
  • 3
    Functional
  • 3
    Server side views
  • 3
    Props
  • 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
  • 4
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    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 · 789.6K 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

45.1K
32.8K
5.2K
Superheroic JavaScript MVW Framework
45.1K
32.8K
+ 1
5.2K
PROS OF ANGULARJS
  • 887
    Quick to develop
  • 587
    Great mvc
  • 571
    Powerful
  • 521
    Restful
  • 503
    Backed by google
  • 348
    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
    Great documentation
  • 23
    Easy to templates
  • 21
    Easy to start
  • 17
    Light weight
  • 17
    Awesome
  • 14
    Javascript mvw framework
  • 14
    Angular 2.0
  • 13
    Great extensions
  • 13
    Efficient
  • 10
    Easy to prototype with
  • 8
    Coffeescript
  • 8
    High performance
  • 7
    Lots of community modules
  • 7
    Two-way binding
  • 7
    Mvc
  • 6
    Clean and keeps code readable
  • 6
    Easy to e2e
  • 5
    One of the best frameworks
  • 5
    Easy for small applications
  • 4
    Works great with jquery
  • 4
    Fast development
  • 2
    Be a developer, not a plumber.
  • 2
    Hierarchical Data Structure
  • 2
    I do not touch DOM
  • 2
    The two-way Data Binding is awesome
  • 2
    Dart
  • 2
    Typescript
  • 2
    Community
  • 2
    Declarative programming
  • 1
    Programming fun again
  • 1
    Acoperișul
  • 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
  • 0
    Httpș//Acoperișul 0757604335
  • 0
    Google.com
  • 0
    Bot Ionescu
  • 0
    Angular js
  • 0
    Js
  • 0
    Oautho loc
  • 0
    Shvzjn
  • 0
    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 · | 25 upvotes · 2.1M 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 · | 20 upvotes · 810.3K 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.3K
2.5K
678
Give your JS App some Backbone with Models, Views, Collections, and Events
6.3K
2.5K
+ 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 · 157.4K 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
Angular 2 logo

Angular 2

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

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 · 277.8K 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
Aurelia logo

Aurelia

258
268
374
Next gen JS framework written with ES6 and ES7. Integrates with Web Components. No external dependencies except polyfills.
258
268
+ 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 · | 5 upvotes · 113K 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
Marionette logo

Marionette

160
118
79
Backbone application code with robust views and architecture solutions
160
118
+ 1
79
PROS OF MARIONETTE
  • 20
    MVC compliant
  • 20
    Uses Backbone
  • 13
    Views management
  • 9
    View management
  • 6
    JavaScript
  • 6
    Memory management
  • 4
    MVC Beginner-Friendly
  • 1
    Collections useful tools
CONS OF MARIONETTE
    Be the first to leave a con

    related Marionette 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 · 157.4K 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
    JSF logo

    JSF

    110
    159
    4
    It is used for building component-based web interfaces
    110
    159
    + 1
    4
    PROS OF JSF
    • 2
      Rich and comprehensive Request Life-cycle
    • 1
      Very Mature UI framework
    • 1
      Server Side component
    CONS OF JSF
      Be the first to leave a con

      related JSF posts

      Hello guys! I would ask for your advice. Our situation is like that there will be a project to revamp workflows and introduce new services like mobile apps, machine learning, and some online services that would use cloud storage. We use JSF, JavaScript, Ajax, Spring, Oracle 12c running on Linux (VM) and providing online services to internal users and the public. But, we are not technically savvy enough to evaluate what tools should be introduced. Personally, I am evaluating whether to take this opportunity to change our practice/PM approach from Prince to Scrum/Agile (It seemed that DevOps is popular) ... Since we adopt ISO 27001 and ISO 20000, security is a crucial factor that we consider. Would you please help to recommend a list of tools and explain the reasons why you recommend them? Thanks in advance~!

      See more

      I need to modernize a Java web application that runs on JSF. I am used to building websites, so Bootstrap kinda feels like "home." But when it comes to applications, I feel Bootstrap is not the right way to go. Can someone explain to me what PrimeFaces is capable of in comparison with BS?

      See more