ember.js Reviews

Convention over configuration

Backward compaiblity and deprecation warnings

Components and services simplicity and flexibility

Pods structure

Ember is very structured, making it clear where things should go. This also means it's able to take care of a lot of wiring automatically, saving time. The developers of the framework are careful to keep backward compatibility and manage feature deprecation gracefully, making it a good long-term investment.

The rigidity of the framework sometimes makes it difficult to implement complex features or interactions. Animations aren't well-supported.

Ember is a great choice for building a complex webapp from scratch.

Ember has a little bit of a learning curve, but once you master that - web apps are so simple to build. With plugins for Rails controller/route generation - you can forget about needing to write complex server side code and focus mainly on the core in-browser app. The data-binding and computed properties make development in Ember so much fun.

Ember is a beast, if there is a bug - prepare to dig into the source code and hunt. The nice thing now is that there are a lot of devs on the project and using the project - much less frequent bugs. If you ever need to write code that breaks out of the pre-defined structure of Ember, that can get a bit more challenging. While there are ways to hop into the pipeline and break the flow, it is an up-hill battle the whole way.

Give it a try! Build an app or two to get your bearings and you will never want to leave.

We initially went for developing web-apps with a great MVC front end and then realized that with the proper tooling, we really only had to write front end code. Back end development became trivial and simple and the teams were able to fly through the projects. The computed properties and data-binding allowed for lots of magic to be written in without having to boilerplate all data object and interfaces.

The best about Ember is Convention over Configuration in its tool - Ember CLI. The organisation and structure of complex projects is great. Also, the components, the bindings, Ember Data, routing, everything together gives great experience of creating complex SPA applications. Ember Data makes it straightforward to work with your API backend and manage models.

Compared to for example Angular I'm happy that Ember comes with Ember CLI. You have best way how to do things shown in the Ember Guides. You don't have to find how to organise project in some tutorial or article like its in Angular, but you can actually jump right to developing applications by running simple command ember new my-new-application.

What I dislike about Ember is its performance compared to other frameworks. Also, sometimes Ember CLI was really painful to work with (you spend hours on struggling with Ember CLI tool instead of developing you application and writing business logic).

Everything. We love Ember.js! It is extremely powerful. Their documentation is awesome. The framework is being updated at a high velocity. They have released stable builds in a timely manner. New features are being added frequently. We use this framework for building powerful web applications.

My company started using Ember.js before it even reached version 1.0. The beginning was a little rough, but now that they have stabilized the framework, it works amazing, and there is nothing to worry about!

Ember.js is extremely powerful. It is easy to create complex applications with large data sets and complicated relationships. If you are trying to manage this type of data on a server level, try Ember and manage everything in the browser!

We wanted an agile framework that was easy to use with an API. Ember.js and Ember Data work beautifully. If you are building a web application with another framework, I highly recommend you consider Ember.js.

I love how opinionated the framework is, as well as the active community of developers. It's amazing how in one command I can have an app set up and ready for development, with all baseline dependencies already up and running. After using it for three years now, I can happily say it is my favorite environment to work in.

The learning curve can be difficult, especially if you have never worked with an MVC or something like it in the past. Though I know the changes are good, sometimes I feel like it is a framework that is moving too fast to keep up with.

Read the documentation on the Ember website. they do a remarkably good job of explaining gotchas and things to watch out for, but most importantly, they explain philosophy around the framework as well as how to use it. The documentation covers everything from generators to testing and deployment, and is pretty clear in how it does everything. Links to the source code where certain features are implemented are everywhere, so you can see what makes the cogs turn if you are interested. Also, check out the Global Ember Meetups and podcasts such as Ember Weekend ad the like. With all these tools, you will do great.

Building software for the death care industry, it is a great tool for passing data around and manipulating it without needing to constantly refresh the page and query the database.

Within an hour new team members know exactly how an Ember application is written by others. ember-cli helps a lot.

You need to invest much time to learn Ember.

Moving Windows applications to the browser.

Ember is MVC based framework. Simple and powerful. CLI as plus for a standalone apps. Good docs and support. Easy to learn if you have any experience with MVC or you are experienced js user. Adapters, json, handlebars\htmlbars(in future) all this cool stuff are included by default. Easy integration with Rails. Best js framework for Rails developer

Repository is updated slowly. Starting Ember.js 2.0 developers reject MVC structure :( Lack of libs\plugins. Hard to keep code up-to-date. Each build comes with hard pack of changes

Take care of Activemodel adapter inherited of json adapter. Complex json strucutre can cause issues

I am building large web apps. Ember.js helps me to share the load between back and front ends.

We were very early adopters of Ember, and I've never regretted it. It's constantly growing and adapting to the needs. It's well-supported, has lots of features, and a very consistent API.

I'd like to see controllers go away, but I don't think there's a good option yet. Honestly, there are very few problems.

We were trying to develop Javascript apps that hit a single Rails back end. Ember makes development SO FAST, especially when using a Rails API.

Coming from the wonderful world of Ruby on Rails, I like the down-to-earth no nonsense design which makes it exceedingly easy to get interactive websites up and running in no time. In addition to the now famous "convention over configuration", there are many appealing aspects. Just to name a few: online guide and API documentation, testing is built in from the start, command line interface ember-cli makes it a snap to create and update projects, there's a wide range of add-ons covering pretty much all you need. The best part is that it's just plain fun to use and there's an enthusiastic community out there to help. If the online guides aren't enough, then there's plenty of information available on the Internet as well as several books.

You probably need to be more experienced with JavaScript, there's a steep learning curve and still some ongoing functionality changes and/or deprecations that need to be taken into account. Sometimes the exact flow is hard to get your mind wrapped around. It helps if you are familiar with ES6+.

Interactive and responsive websites which work well across various devices. Write once and single deploy saves time and money.