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.
Comments
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.