Need advice about which tool to choose?Ask the StackShare community!


+ 1

+ 1
Add tool

Angular 2 vs Ember.js: What are the differences?

  1. Architecture: Angular 2 follows the component-based architecture where every element on the web page is considered a component, making it more organized and easier to maintain. On the other hand, Ember.js follows the Convention over Configuration (CoC) approach where developers need to follow specific conventions to build the application, making it less flexible but faster to set up.

  2. Learning Curve: Angular 2 has a steeper learning curve compared to Ember.js due to its complex syntax and concepts such as RxJS and TypeScript. Ember.js, on the other hand, is known for its simplicity and ease of learning, making it a better choice for beginners or those looking for quick prototyping.

  3. Community Support: Angular 2 has a larger community and a vast ecosystem of libraries and tools, providing better support for developers facing issues during development. Ember.js, while having a smaller community, has dedicated contributors who ensure continuous improvement and updates to the framework.

  4. Flexibility: Angular 2 offers more flexibility in terms of customization and extensibility, allowing developers to fine-tune the application according to their requirements. Ember.js, although less flexible compared to Angular 2, provides a more opinionated structure that can speed up development by reducing decision-making processes.

  5. Data Binding: Angular 2 uses two-way data binding by default, meaning changes in the model are automatically reflected in the view and vice versa. Ember.js, on the other hand, uses one-way data binding by default, making it easier to trace data flow but might require more effort in updating the view when the model changes.

  6. Performance: Angular 2 is known for its better performance in handling complex and dynamic web applications, thanks to its advanced features like Ahead-of-Time (AOT) compilation. Ember.js, while efficient in rendering templates and handling data, can sometimes struggle with performance when dealing with large-scale projects.

In Summary, Angular 2 and Ember.js differ in architecture, learning curve, community support, flexibility, data binding, and performance, making each suitable for different development needs.

Decisions about Angular and Ember.js
neha menahil

Have you ever stuck with the question that which one is the best front-end framework for you?

With continuous web development progress, the trends of the latest front-end technologies are also continuously changing with more and more sophisticated web features. These top front-end frameworks and libraries have made your complex web tasks more flexible and efficient.

Check out top front end frameworks and their features at

See more
Dennis Ziolkowski

I was first sceptical about using Angular over AngularJS. That's because AngularJS was so easy to integrate in existing websites. But building apps from scratch with Angular is so much easier. Of course, you have to build and boilerplate them first, but after that - you save a ton of time. Also it's very cozy to write code in TypeScript.

See more
Julius alvarado

It is a complete waste of time and life to learn a different framework to solve the same problem (Both AngularJS and Angular build A+ UI's, but both require a lot of time to learn). It's dumb to spend 200 hours learning AngularJS, then 200 hours learning Angular when you could spend 200 hours learning AngularJS and 200 hours learning how to solve a different problem (like AI/ML, Data Science, AR/VR, Digital Marketing, etc.)

See more
Kyle Harrison
Web Application Developer at Fortinet · | 2 upvotes · 48.2K views

When deciding on a front end framework to build my bitcoin faucet project, I knew I needed something battle hardened, dependedable, but also feature filled and ready to go out of the box.

While I've written some smaller apps with ng2+, I've never gone full tilt with it so I knew there were still some things to learn, and most importantly: how to do them properly, such as proper component architecture and breaking old habbits from ng1.

I didn't opt for React in this case, simply due to the need to stack more and more things on top of it to do what I'd need it to do. I wanted a framework that was going to take over routing and execution of complex UI controls, and keep items outside of a component's scope updated and react to events. This framework needed a comprehensive event emission system, data acquisition and handling, bi-directional data binding, state, and a series of things that you'd need to install separately for React to match up to what's already in the box with Angular.

I opted to stick to Angular instead of Vue for the fact that Angular also already has it's entire build system ready to go and comprehensivly built to deliver the tiniest version of it's deliverable. I was hosting this thing in a google cloud instance, so I needed to make sure the app stayed as small as possible, and could automatically trim out the cruft. This is where Angular's built in Tree Shaking took precedence for me.

Vue is more than capable of handling everything I'd need, and it was something I took serious considerion of. For instance, Vue poweres Cointiply, another bitcoin faucet application that's highly reactive and high componentized just like I wanted.

But I'd still need to learn Vue, I'd still need to configure it's build system, and I still wanted to use SCSS and TypeScript.

So Angular it was. ng8 is a great platform for building very complex user interfaces, and has many of the problems you'd inevitably face integrating a user interface to an application already figured out, and complete with a best practice recommendation.

React and Vue, given enough time and energy, are super capable platforms. No one can deny that. Angular's "A-Z Batteries Included" approach to the whole development process is what made it especially enticing this time.

See more
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Angular
Pros of Ember.js
  • 109
    It's a powerful framework
  • 53
    Straight-forward architecture
  • 48
  • 45
    Great UI and Business Logic separation
  • 40
    Powerful, maintainable, fast
  • 39
    Amazing CLI
  • 33
    Great mvc
  • 29
    Powerfull Dependency Injection
  • 19
    Easy to build
  • 16
    All in one Framework
  • 15
    Opinionated, batteries-included approach
  • 11
  • 10
    Solid Standard Setup.
  • 8
  • 7
  • 5
  • 4
    Only for single page applications
  • 3
  • 2
  • 2
    Ng upgrade
  • 1
  • 126
  • 97
    Quick to develop
  • 83
    Great mvc
  • 82
    Great community
  • 73
    Great router
  • 52
    Values conventions, there is one-true way to organize
  • 50
    Open source
  • 44
  • 34
    Mvc framework
  • 28
  • 13
  • 11
    Yehuda katz
  • 10
    Tom dale
  • 10
    Great logo
  • 6
    It's NOT Google or Facebook
  • 5
    manages large data sets on the front end easily
  • 5
    Convention over Configuration
  • 5
    Glimmer: react-like rendering engine
  • 4
  • 4
  • 4
  • 4
  • 4
    It rocks
  • 3
    Good docs
  • 3
    Fastest spinning circles
  • 3
    IE8 support
  • 2
    Easy and Quick to develop
  • 2
    Documentation is finally active and updated
  • 1
  • 1
    Business wins
  • 1
  • 1
    Great for big apps/many devs because its organized
  • 1
    Growing community
  • 1
    For building ambitious Web apps
  • 1
    Dependency Injection
  • 1
    Stability without stagnation

Sign up to add or upvote prosMake informed product decisions

Cons of Angular
Cons of Ember.js
  • 9
  • 9
    Large overhead in file size and initialization time
  • 2
    Ugly code
  • 2
    CLI not open to other test and linting tools
  • 2
    Very little flexibility
  • 2
    Too much convention, too little configuration
  • 1
    Hard to integrate with Non Ruby apps
  • 1
    Hard to use if your API isn't RESTful

Sign up to add or upvote consMake informed product decisions

What is Angular?

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

What is Ember.js?

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.

Need advice about which tool to choose?Ask the StackShare community!

Jobs that mention Angular and Ember.js as a desired skillset
What companies use Angular?
What companies use Ember.js?
See which teams inside your own company are using Angular or Ember.js.
Sign up for StackShare EnterpriseLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Angular?
What tools integrate with Ember.js?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

What are some alternatives to Angular and Ember.js?
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 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 is a next generation JavaScript client framework that leverages simple conventions to empower your creativity.
It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.
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.
See all alternatives