Everyone Who Tried to Convince Me To Use Ember Was Wrong

Nowhere does the article say what problem the author was actually try to solve by switching to Ember. It sounds like his only reason for this painful experience was that he didn't want to the last one in his group of friends who wasn't using this cool, new framework. And that's not a good basis for a business decision.

> Can you tell me a way to switch that will not significantly reduce my productivity for the first few weeks.

The only way I can imagine doing this is to time-travel and give myself a crash-course in all the stuff I struggled to figure out in the beginning. Now I feel like I could give myself a complete tutorial in a day.

The trouble is partly that everyone coming to Ember has a different way of thinking, and the documentation can't target all the sets of prior skills and assumptions. I always thought that for a great book, the reader should meet the writer half-way. In this case, however, the reader has a long way to go before they can move easily through the range of Ember's capabilities.

I'm glad that you finally found a way to get up to speed. I find it very challenging helping people over the initial jump of Ember learning so any feedback about what worked for you is great to have.

I'll probably have lots of conversations about this next week at Emberconf!

I need an Ember expert to compare it to ExtJS. I've skimmed over Ember. It feels like it'll take the same amount of pain as ExtJS to get through it, but the overall feature set is inferior.

Connery seems to make his mark by being a professional douchy complainer. Just saying take whatever he says with a dose of "if I didn't write it, it sucks" type attitude.