rxcfc

8 ms·

31.
by rxcfc 14y ago
I agree that Trek's response here is not very helpful. However he has spent countless hours working on Ember's documentation and the fact that it's where it is now is due to his dedication. There's clearly more work to be done and we're all
32.
by rxcfc 14y ago
Unfortunately, no such diagram exists though it would certainly be useful. The lack of documentation is tied a lot to the instability of the Ember Data API, both of which are reasons why it hasn't had a formal release yet.
33.
by rxcfc 14y ago
It's not quite a shorthand as the controller can have properties of its own as well. However, the general understanding is correct, the controller proxies to the content. The controller is not the data, but it acts like it.
34.
by rxcfc 14y ago
Are you implying that Ember doesn't deliver on this desire to build desktop class applications in the browser? If so, can you explain where it falls short?
35.
by rxcfc 14y ago
Creating an Ember Object is very simple: `Ember.Object.create(properties)`. If you want, you can subclass `Ember.Object` and then `create` an instance of your subclass. The main benefit to using `Ember.Object` is that you get convenience me
36.
by rxcfc 14y ago
Ember is built to work with Ember Data out of the box, but it's trivial to make your own methods that fit with the conventions. I assume you're referring to the default `find` support in the router. All that Ember does is attempt to infer a
37.
by rxcfc 14y ago
The Ember teams has been planning for a sweep of all outdated information about Ember. We'll be updating SO questions and asking blog authors to add a disclaimer. Ember Data is a completely optional component of Ember that seeks to bring OR
38.
by rxcfc 14y ago
I understand how that would add a bit of overhead, but it doesn't seem all that crazy. Certainly a well architected client app wouldn't have any issue with this. Maybe I'm missing something?
39.
by rxcfc 14y ago
This is actually something I think can be solved. There have been some experiments in Ember with building Ember model definitions from the server model definitions. However, in practice I haven't found this to be much of an issue in my deve
40.
by rxcfc 14y ago
That's a good point. We probably should add a section on helping users decide whether Ember is a good fit for their goals. While there's obviously some disagreement in this area, we can at least make it clear what sort of apps we intend Emb
41.
by rxcfc 14y ago
If it's double the work, you're doing it wrong. Possibly it's not a good fit for your specific case, or you haven't fully understood the best way to use it.
42.
by rxcfc 14y ago
"we did live (email) thread locking and all kinds of crazy stuff" - Can you say more about what this entails?
43.
by rxcfc 14y ago
If you're building the kind of app that Ember is designed for, all of the above will be true. But we never anywhere claim that Ember is the right solution for every webapp. There's a definite type of app that doesn't benefit from Ember and
44.
by rxcfc 14y ago
This talk I gave last year describes some of the problems that Ember attempts to address that libraries like Backbone don't: http://vimeo.com/49434697
45.
by rxcfc 14y ago
We were in the middle of the release yesterday. If anything is still not matching, please let us know so we can correct it.
46.
by rxcfc 14y ago
a) Are you proposing that Ember should have stayed SproutCore? To date, Ember has been far more successful than SproutCore and the split has enabled us to make progress that could not have been made otherwise. b) The Ember developers also h
47.
by rxcfc 14y ago
It all depends on what kind of app you're writing. If you're happy with whatever solution you're using then it's foolish to change just for the sake of change. However, I've known multiple developers who started with Backbone and then found
48.
by rxcfc 14y ago
We know that a getting started guide is essential. It's a high priority for us and we actually worked on it today.
49.
by rxcfc 14y ago
The docs are actually quite good now. As we've just released 1.0 RC, the API is also frozen which will help the docs improve even further.
50.
by rxcfc 14y ago
This was only true briefly. The guides on emberjs.com reflect the currently released version, 1.0 RC. Since we've hit RC the APIs are now frozen.
51.
by rxcfc 14y ago
Prior to the 1.0 RC, Ember's API changed a lot because we were seeking for the best abstractions. We didn't want to lock ourselves in when there was a better way to do things. Now that we've hit 1.0 RC, the API is generally frozen. We'll on
52.
by rxcfc 14y ago
Ember has changed quite a bit from its SC roots. I would probably use Angular over SC myself, but if given the choice to use Ember would much rather use it.
53.
by rxcfc 14y ago
This is a good post on why Discourse chose Ember: http://eviltrout.com/2013/02/10/why-discourse-uses-emberjs.h...
54.
by rxcfc 14y ago
This is a great post on why one project chose Ember: http://eviltrout.com/2013/02/10/why-discourse-uses-emberjs.h...
55.
by rxcfc 14y ago
Things like this make me extremely wary of Angular's DI: http://www.alexrothenberg.com/2013/02/11/the-magic-behind-an...
56.
by rxcfc 14y ago
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.
57.
by rxcfc 14y ago
I'm pretty confident in Yehuda and Tom's ability to figure things out. It's a very difficult problem to solve, as evidenced by the slow pace of progress, but I think it is a solvable one.
58.
by rxcfc 14y ago
Certainly unfinished. Unlike Ember, Data hasn't had any releases. There's a reason for this. We don't think it's stable enough to recommend to anyone unwilling to do some hacking.
59.
by rxcfc 14y ago
Sorry about this, we're going to be cutting a new release soon so that should resolve this discrepancy.
60.
by rxcfc 14y ago
More guides are in progress.

More ›