| > Our development speed was about 1/3 of what it would have been with normal rails development. How much experience did you already have with Rails? I would expect that learning a new tool would take longer than using one you are already intimately familiar with. > Additionally, using Ember really increased the layers in our stack. I don't think this is that much different than Angular.js. That would also add a significant number of components to the stack. > Writing most of your app in JavaScript is simly not fun. Typos aside, this is hardly a downside of Ember.js. I work in JavaScript full time (node.js), and while it has its gotchas, I really appreciate the functional nature of the language. I was writing some C# yesterday and I was disappointed at how hard it was to do function passing and function composition compared to JavaScript. It's good for the Ember.js ecosystem to understand the short comings of the framework, but I don't think it's particularly useful to say "Don't use this tool because...". The fact that people DO use the tool means that some people do find value in it. One of the complaints is that there isn't enough sample code posted, yet this post didn't provide any sample code of their issue or their solutions. Doing that would add more value than just saying "Don't use Ember." |