Angular worked far better for me
Ember.js or Angular.js?
51–60 of 104 posts
Re: Ember.js or Angular.js?
#52I actually really like the KnockoutJS + SammyJS approach to building single page apps. Angular is probably closer to that approach.
MVVM is awesome and will save you a lot of time IMO.
Re: Ember.js or Angular.js?
#53Earlier quoted context omitted.
I believe almost all of them have this capability. I know angular has templates and you can put dynamic data in those templates. The dynamic data can be loaded from anywhere. I'm not aware of any MVVM that doesn't allow you to do this, unless I misunderstand what you are saying.
I guess I wasn't clear enough. You're talking about data -> template binding. I'm talking about the reverse, where some data (as a model) is recovered from a partial server-side render of the page, based upon the "patterns" described in the templates. For example, if Angular did this (I don't think it does), it could traverse the generated HTML and compare it with the original template to figure out what's what.
I haven't explored what your describing, but I'm using a different solution. I'm adding backbone to an existing project and added some server side code that outputs the current model object as json in a tag in the html page. This is passed to a new backbone model instance.
Re: Ember.js or Angular.js?
#54I actually really like the KnockoutJS + SammyJS approach to building single page apps. Angular is probably closer to that approach. MVVM is awesome and will save you a lot of time IMO.
We're currently using Sammy + Knockout on https://circleci.com, and it is nice, but adding observables everywhere is annoying. I'd love to hear from anyone who moved from this to Angular or Embed?
Re: Ember.js or Angular.js?
#55I 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 wasn't trying to scare people off of angular, as it's what I am currently trying to use. I find it to be a very good framework, but also plan on checking out ember.js to see if it provides more for me overall or not.
Re: Ember.js or Angular.js?
#56Earlier quoted context omitted.
Looks like the peepcode screencast is paid: https://peepcode.com/products/emberjs I suppose you'll say it's well worth the money? Anyone else bought/watched this screencast?
Definitley worth the money but for my taste a bit too basic
Bought it, and yes it worth the money and is a bit too basic. I think they are planning to do a sequel with more advanced topics, especially regarding ember data.
Re: Ember.js or Angular.js?
#57I've used SC before it was Ember, hated it. I've been using Angular for a few weeks - LOVE it. It's amazingly quick to build great stuff. I was on a Skype call with my UX designer the other day talking about how we should display a permissions list: we sent back and forwards a few different sketches, by the time we finished discussing the final sketch I had reimplemented the modal as a radio button, disabling and hid…
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.
Re: Ember.js or Angular.js?
#58ok here is my take : AngularJS : + MVVM : databinding + Dependency Injection, so no global state, and loose coupling + Well organised into services , view models ,directives , filters , ... - forget any projects that are animation/transition between views heavy, you'll fail - doesnt play well with some other frameworks ( requireJS, jQuery mobile , even phonegap ...) - is slow when dealing with a lot of data. - no con…
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 only break existing APIs in exceptional cases. Once 1.0 Final is release we'll be sticking to SemVer.
Re: Ember.js or Angular.js?
#59I tried both in similar circumstances (coming from a long backbone background), all I can say is I personally found with Ember.js (around august 2012): - more boilerplate - learning curve was much steeper. - the documentation confused me, it turned out there were many slight diferences between 0.9.xxx and 1.xxx. This "gotcha" is probably rectified by now I tried Angular.js next (this month) and "got it" immediately:…
> 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.
Re: Ember.js or Angular.js?
#60I want to learn Ember, but the official docs are confusing, and the tutorials are outdate, are there any YouTube videos or any other of tutorial on Ember?
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.