71–80 of 104 posts
It would be unfair for me to compare this experience to Angular though because I haven't been so deeply involved with it.
Earlier quoted context omitted.
> forget any projects that are animation/transition between views heavy, you'll fail Animation is coming to the next version. It's already possible but you have to do it yourself. > doesnt play well with some other frameworks ( requireJS, jQuery mobile , even phonegap ...) * https://github.com/tigbro/jquery-mobile-angular-adapter * http://briantford.com/blog/angular-phonegap.html > is slow when dealing with a lot of…
> * https://github.com/tigbro/jquery-mobile-angular-adapter * http://briantford.com/blog/angular-phonegap.html that's what i'm saying i should not need an adapter for these libraries , i dont need them with Ember or Backbone
I have limited experience with javascript and MVMM's and cannot answer all the questions, but here is what I do know: Which is best overall? Not enough experience with ember.js to comment. Common gotchas for angular: It's a very different approach when compared to using jquery for everything. The documentation can seem a bit daunting at first, as described in the popular post about why discourse chose ember.js. "The…
Ha ha, nice way to scare people off angular and justify their decision ;) Transclusions are an interesting feature to cherry pick because a) they're a necessary complexity to enable reusable components (one of angular's greatest strengths), and b) they highlight the steep learning curve required to truly master angular. I agree that the docs can be a bit vague occasionally, but I think that's only due to the sheer de…
I have limited experience with javascript and MVMM's and cannot answer all the questions, but here is what I do know: Which is best overall? Not enough experience with ember.js to comment. Common gotchas for angular: It's a very different approach when compared to using jquery for everything. The documentation can seem a bit daunting at first, as described in the popular post about why discourse chose ember.js. "The…
Actually that's the only bit confusing part of the documentation (which now everyone is quoting to troll Angular).
I think deciding on this will be hard and frankly subjective. My suggestion is that you try both for a small project and decide for yourself what makes you feel at home. It should not take more than a couple of days to assess it yourself. As for me, I decided to go with Ember.js. To be frank the final decision was between Ember and Angular (over all other frameworks) and I felt that getting past the learning curve of…
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.
Earlier quoted context omitted.
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.
The guides are good, but I'm missing the whole put it all together to make a real app tutorial type level of documentation. Can you point me to something like that?
https://github.com/addyosmani/todomvc/tree/gh-pages/architec...
Earlier quoted context omitted.
> This "gotcha" is probably rectified by now It's not. The guides published on emberjs.com apparently track the master branch on github, so are regularly out of sync with the version offered for download on the front page, and at the moment there's a third version bundled with the starter kit. This completely tripped me up when I tried to get off the ground a couple of weeks ago, because things that were described as…
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.
I'm glad the APIs are frozen, I was worried there'd still be creep through the RCs.