[eduardordm]

Your comment is among the sanest in this thread, thanks.

The single most important thing you said is: "It should not take more than a couple of days to assess it yourself."

If you are a serious web developer, you should know the basics of both, they are both great in their own way. Every project have its own requirements and sometimes both libraries will not be suitable, sometimes you will want to go with backbone or something else.

I would recommend going to peepcode.com and egghead.io before jumping into the docs.

I will just leave this here and bail out: I have a hunch ember.js will become a default in RoR by the end of this year.

[atomical]

What do you mean by default?

[jlogsdon]

It will be a part of the generated Gemfile, much like coffeescript is now.

[atomical]

It seems unlikely based on the views of rails core.

[mattmanser]

I suspect in a couple of years time no-one will be using ember.js as it presently is.

They use methods to access properties and hide the actual properties away in an internal array.

This is because ECMA 3 doesn't have get/setters for property changed notifications. It's one of those things you can't shim. ECMA 5 does support get/setters, so once you don't have to support IE8, using it as it presently is will be silly.

It's a ticking time bomb. If you're using ember.js you can't write normal javascript, which is why I think it won't get any serious penetration. Or I hope it doesn't anyway as I've used libraries that do this before and it gets old fast.