Starting out with Ember.js is a lot like starting out with Rails -- there is a plethora of ways to achieve one thing. This is a good thing and a bad thing. It's good that the framework is flexible enough to support multiple and solid ways of implementing a feature, however, with a large team, a convention needs to be established for maintanability and overall sane-ness. So why not stick with the framework's conventions?
Your new post is loading...