News for hackers. Stuff that matters.
Re:Ember.js 1.0 RC1 released by scotth on Saturday February 16, 2013 @01:08AM (#5230596)
Can't beat it? It's good, but Angular.js is definitely a front-runner.
Re:Ember.js 1.0 RC1 released by jetako on Saturday February 16, 2013 @03:25AM (#5230874)
I chose Ember in part to make use of its sibling framework, ember-data. Is there a relational model abstraction that integrates well with Angular?
Re:Ember.js 1.0 RC1 released by rxcfc on Saturday February 16, 2013 @01:11AM (#5230601)
I think if we're going to start this debate that we need to substantiate the claims on both sides. This is probably not the ideal place for that debate, however.
Re:Ember.js 1.0 RC1 released by ninetax on Saturday February 16, 2013 @01:19AM (#5230613)
On the contrary, I'd love to hear the debate! If not here then where?
Re:Ember.js 1.0 RC1 released by codygman on Saturday February 16, 2013 @01:28AM (#5230637)
Re:Ember.js 1.0 RC1 released by ninetax on Saturday February 16, 2013 @01:34AM (#5230651)
Ah, thank you very much.
Re:Ember.js 1.0 RC1 released by camus on Saturday February 16, 2013 @01:13AM (#5230607)
they are very differnt , DI is great but all the directive lifecycle pisses me off sometimes. and dirtychecking on huge collections? without a native Object.observe it is slow.
Re:Ember.js 1.0 RC1 released by wycats on Saturday February 16, 2013 @01:24AM (#5230628)
For what it's worth, it's not clear how Object.observe will substantially improve the performance of large collections.

For example, if you insert an item at position 0 of a 10,000 item array, Object.observe will publish a change for every item (since they are all moved one item down). It is then up to the receiver of those changes to reverse engineer what exactly happened (which is slow).

What is needed is Array observers, which would notify the index of the change, number of items removed, and any items added (the `splice` signature). Ember emulates this, but by using a different API than the normal Array API. I hope that future extensions to Object.observe will support Array observation.

As a member of TC39, I worked closely with several members of the Chrome team on Object.observe and hope to work with them again on an Array extension to the spec to make Array observation faster. I yearn for a future where Ember can get good performance without having to ask our users to use an alternative API.

Re:Ember.js 1.0 RC1 released by wolfhumble on Saturday February 16, 2013 @01:20PM (#5232392)
> I yearn for a future where Ember can get good performance without having to ask our users to use an alternative API.

Could you explain what you mean by: ". . . ask our users to use an alternative API"?

Thanks!

Re:Ember.js 1.0 RC1 released by sandstrom on Saturday February 16, 2013 @08:33PM (#5233857)
I think he's referring to the get/set accessors (e.g. `myObject.set('foo', bar)` instead of `myObject.foo = bar`).

Here are some resources:

# http://emberjs.com/guides/object-model/classes-and-instances...

# http://jfire.io/blog/2012/04/19/why-ember-dot-js-doesnt-use-...

# http://emberjs.com/api/classes/Ember.Array.html

Re:Ember.js 1.0 RC1 released by rxcfc on Saturday February 16, 2013 @01:21AM (#5230617)
Things like this make me extremely wary of Angular's DI: http://www.alexrothenberg.com/2013/02/11/the-magic-behind-an...