Last week one of our PHP developers presented the pros and cons of Ember.js, prompting a team discussion centered around the idea of whether or not to move in this direction. Ember is an open-source client-side JavaScript web application framework. It allows developers to create single-page applications that are scalable. Ember was created in 2011 by Yehuda Katz who is a member of the jQuery, Ruby on Rails and SproutCore core teams.
During our meeting, we discussed how good design has always been a matter of form following function but somewhere we lost sight of that on the web and by using Ember, this could be made a possibility again. Ember has a real application router layer, model layer, view layer, controller layer, data layer with custom adapter support and it has support for mixins, web components, helpers, sanitizers and CLI addons. One definite pro is Ember provides sane naming conventions that do a lot of the work for you. It provides a directory structure and a sane way of organizing your code. Additionally, Ember helps you to not sweat the small stuff because that’s what the frameworks are for and often has what you need before you even know you need it. The Ember applications are easy to upgrade with great in-line documentation warning of deprecations so developers can write clean code the right way, the first time.
This was just one of many conversations to come regarding Ember. However, this meeting provided an insightful dialogue regarding a potential new direction for our team. For more information, check out the link below to view the original presentation from our meeting.
http://www.slideshare.net/KrisHedges/emberjs-a-clear-route-to-a-modern-web