That post is unfortunately incorrect. The author claims that AngularJS doesn't have "composed views" which is very unfortunate because out of all the frameworks he listed Angular's component composition model is by far the best, he just didn't bother to investigate it despite several users pointing out the error in the discussion under the post.
It also mentions that "asynchronous UIs" (ie, optimistic save: server callbacks don't block, if something bad happens you'll solve it in a callback) need some sort of operational transformation (think google wave), but I think this only applies if you are writing real-time multi-user apps (chats, google docs, etherpad, etc) which is the overwhelming minority of mobile apps.
One of the design goals of AngularJS is to be as close to HTML and browser as possible - picking the good parts and enhancing it for building web applications.
Not digging against you, but this might (though, imho it shouldn't) be a barrier to entry to newcomers. I've simply resigned myself to editing the one line it takes to complete the tutorial every step of the way... Though in retrospect I think I probably could have just forked it and updated that line myself for a permanent fix... :)
Sorry, Igor. I jumped the gun with that post and have managed to develop my app in a few days :)
I thought the documentation is pretty excellent. The tutorial did help with some of the concepts but it could be that my project requirements are different and so I didn't find it entirely helpful :)
That said, I found the cookbook to be helpful although it seems like it's not linked anywhere from the homepage?
Comments
I'm interested in this too, I did find a blog post which does some comparisons: http://codebrief.com/2012/01/the-top-10-javascript-mvc-frame...
That post is unfortunately incorrect. The author claims that AngularJS doesn't have "composed views" which is very unfortunate because out of all the frameworks he listed Angular's component composition model is by far the best, he just didn't bother to investigate it despite several users pointing out the error in the discussion under the post.
It also mentions that "asynchronous UIs" (ie, optimistic save: server callbacks don't block, if something bad happens you'll solve it in a callback) need some sort of operational transformation (think google wave), but I think this only applies if you are writing real-time multi-user apps (chats, google docs, etherpad, etc) which is the overwhelming minority of mobile apps.
Thanks a lot - that link was really helpful!
I was reading through AngularJS and was utterly confused - it sounds a bit too complexed for my needs at the moment.
Really? Have you watched any of the videos on the http://angularjs.org/ home page? Or taken our awesome tutorial: http://docs.angularjs.org/tutorial
One of the design goals of AngularJS is to be as close to HTML and browser as possible - picking the good parts and enhancing it for building web applications.
I'm very excited to try Angular. Your tutorial, however, is not compatible with the suggested server experience where Apache is not installed, as Node has updated to v0.8 and not only deprecated but removed the "sys" module in favor of the "util" module. Update your repos please? https://github.com/angular/angular-phonecat/pull/18 https://github.com/angular/angular-seed/pull/22
Not digging against you, but this might (though, imho it shouldn't) be a barrier to entry to newcomers. I've simply resigned myself to editing the one line it takes to complete the tutorial every step of the way... Though in retrospect I think I probably could have just forked it and updated that line myself for a permanent fix... :)
Will get this fixed ASAP. Node 0.8 is only ~1 week old ;-)
Sorry, Igor. I jumped the gun with that post and have managed to develop my app in a few days :)
I thought the documentation is pretty excellent. The tutorial did help with some of the concepts but it could be that my project requirements are different and so I didn't find it entirely helpful :)
That said, I found the cookbook to be helpful although it seems like it's not linked anywhere from the homepage?