Aurelia vs Ember

Full support for Typescript built in

Clear, intuitive and HTML/SVG compliant binding syntax.

Examples:

Default binding => value.bind

One Way binding => value.one-way

Two Way binding => value.two-way

One Time binding => value.one-time

Configured to give you the most common use cases by convention, which means you only need to change the default configuration for edge cases. This means that for normal cases far less boiler plate code has to be written.

Aurelia includes native support for ES6 and even comes with a Gulpfile which helps with transpiling ES6 code to ES5.

Aurelia is extremely unopinionated and was designed to be highly modular. This gives the developer the freedom to develop their application however they want, without forcing them in paradigms or rules predefined by the framework. Likewise, any of the individual components can be swapped out if so desired.

Aurelia developers always try to keep within existing and emerging Web Standards, making it easier for developers to follow best practices in web development.

Most of the code you write is Aurelia-agnostic. It's one of the closest libraries that you'll find to basically write plain-old, vanilla Javascript or TypeScript code (classes) and doesn't polluate your HTML/SCSS. That way you can easily test it, switch to another implementation and make it look clean (business oriented). Even the HTML.

Learning aurelia basically means learning EcmaScript and HTML, since aurelia is designed for standards compliance. Also, aurelia embraces upcoming ES language features by convention, such as ES class decorators for dependency injection, encouraging clean architecture and future-proof code.

The syntax used to bind variables within the application class is very similar to Javascript itself. You can specify the type of the binding you are using explicitly, which practically self-documents your code and makes it easy to understand whether a value is one-way or two-way binded.

Aurelia.js consists of modules that can be used as a full framework or separately.

One of the most crucial pieces of any new technology or framework is the documentation. At present even though Aurelia is pre-beta, the documentation is pretty complete. There are code examples missing and whatnot, but for the most part it is concise and makes the main parts of the application easy to understand.

Aurelia is officially backed by Durandal Inc. and has commercial and enterprise support is available.

Aurelia defaults to one-way data binding, alining with conventional wisdom. However, there are times when two-way data binding proves useful, such as binding an input widget with a view-model. Aurelia makes two-way data binding available to developers and uses it by convention when appropriate.

Aurelia can be used alongside of React and Polymer, since it is designed for interoperability. In practice, this means Aurelia developers can use React components by including an Aurelia custom element:
https://github.com/Vheissu/aurelia-react-example/blob/master/README.md

It also works well with Polymer, since they are both based on the WebComponents standards:
http://aurelia.io/hub.html#/doc/article/aurelia/framework/latest/integrating-with-polymer

https://github.com/aurelia/cli
The CLI helps rapid creation of projects with generators, building, deploying and hot reloads. Webpack should be coming soon.

The Aurelia community is growing at a great pace. Still doesn’t rival the big players line Angular or React, but the answer to an Aurelia issue is a quick question away on their Discourse.

With dependency injection, you can load in extra javascript and new functionality just when you need it.

This is particularly helpful with testing as you can swap out services for test services.

It also means in single page apps you can load dependencies only as you need them instead of loading them up all up at the start.

Ember already defines the general application structure and organization for you. This was done to prevent developers from making mistakes which would needlessly over-complicate their application. While it's still possible to go out of these practices forced to developers by the Ember authors, you still have to go out of your way to force them.

Ember-CLI is a very useful tool. With just a couple of commands it scaffolds the code, installs dependencies and finally compiles everything itself. It's very useful to quickstart an Ember project.

Ember's preferred templating language is Handlebars. This is mainly because Handlebars is a logic-less templating language and Ember tries to keep it's logic outside the view.

Another reason why Ember benefits from Handlebars is mostly aesthetic as Handlebar's clean syntax makes for easier to read and understand templates.

Finally, Handlebars templates are compiled instead of interpreted, which means that they are much faster to load.

Ember follows the philosophy of "convention over configuration" meaning that it already has almost everything configured for you, so you just have to start coding and developing your project right away.

Ember is practically a complete full-stack front-end framework. It comes with it's own asset pipeline, router, services etc...

The Ember Guides are well structured and very well written. The API documentation is also fantastic.

Most of Ember's components come from the Ember Object Model. It's the basis for views, controllers, models and even the framework itself. This means that the framework is extremely consistent since almost every component shares the same core functionalities and properties since they are all derived from the same object.

Route handlers for the URLs can see a wide range of possible application states, asynchronous logic in the router makes sure of Promises. And implementing makes sense.

It batches bindings and DOM updates to increase performance; if similar tasks are added to a batch, the browser would only need to process them in one single go, as compared to re-computing for each task one at a time.

Ember's API are really easy to understand and work with. It has methods which allow you to harness complicated functionalities in an easy to understand way.

Ember's new router need much less boilerplate code that it previously did.

Ember also has a debugging tool called Ember Inspector which is used for debugging the client side of your app.

You can use any of jQuery’s features.

EmberJS provides with an extremely handy feature of advanced bindings. With this you can not only set the path to the binding value in your app but also set in which direction you want the changes to propagate to (oneway, single, multiple etc).

Promises represent an eventual state in asynchronous logic. Having promises everywhere (almost) means you could write simple and modular code, using almost any API that Ember provides.

Having custom properties in your templates is itself a huge plus but having custom computed properties is an even greater benefit, since now you can code your custom function as a property and call it from your template. Hence rendering your page exactly according to your needs.

Ember comes with built-in routing capabilities. There's no need to install third-party plugins to be able to use routes.

If you've used handlebars (Ember.js's templating is powered by HandleBars) helper tags in your code (like {{#each}}) you won't have to worry about updating your template each time you add/remove data from your page, Handlebars will auto update your template for you.