[ekidd]

My business is based on delivering good applications very quickly. I recently delivered an Ember.js application, and my client said, "I feel like I just won the lottery."

This was largely thanks to the fact that once I climbed the Ember.js learning curve, certain kinds of features became ridiculously easy to implement, and I had enough time to plow through the remaining problems with brute force. I also learned that (a) the unreleased Ember Data library is actually pretty good, but (b) getting into fights with Ember Data is catastrophic and never ends well. When Ember Data wants something specific, I fix the server to provide it and I don't argue.

But no, there's no way you can go look at a job board and find Ember jobs. It's more like how I remember Rails 0.13—there's an opening for certain aggressive businesses to develop software more quickly than before, but the tools are immature and there's not really a well-established job market yet.

[meric]

How long is the Ember.js learning curve? Can you use it in an existing project? (Without replacing a large part of existing code)

Asking because I might have some influence over what technologies our company might use in the near future.