Foxandxss

It is indeed faster but I am sorry to say that this is a good example of "How to not develop an angular app".

DOM manipulation in a controller is something you can't do and who says controllers, says services too.

On the other hand, the double ng-repeat could be a hot spot for the bad performance.

Don't get me wrong, the app is awesome, awesome idea but the implementation doesn't respect the angular way so it is really slow.

Would be good to have a real-world example, like a progress for $http, or loading data... I am trying to swap angular-app's spinner with this, but it works with $http.pendingRequests (the less, the more advanced the progress should be).

Did anyone said awesome? Well, I will: Awesome.

Hello friends, I updated the post with your new insights. I hope you find it better. If not, please reply all you need or even better (Make some pull requests :P).

As I said in the first post, I am the first who is learning Angular.js but I find that teaching what are you learning is the best way to learn. So here am I teaching the best I can.

Of course, there is things that I ignore, so I really appreciate all your comments, so I learnt a LOT about services today.

Thank you.

Interesting, I am updating the post to cover this too.

I really appreciate your answer. As I said in the first post, I am a learner too, so I will update it with your insights :)

Well, not that complex, I just tried to show the minimum things possible. My first idea for a service was a twitter search but that implies an explanation of $http and things related with it. Auth request are not that bad, it is certainly not as simple as we want (but that happen in every client side framework) but not bad. I want to cover auth in a future article.

True, but the directive will reach to those places where html5 is not a welcome guest.

But to be sincere, I picked one thing to a directive, there are infinite ideas but I needed one easily enough for a "hello-world" type of post.

You made a good point here. That point of view will prove to be useful to me :)

It came with the theme, I lack design skills but so far is not that bad and I don't have any flickering...

I agree with you.

I don't feel I have the experience to write better angular docs. That could be a goal in a future for sure.

Even when I am going to write about things that could be used to improve the official docs, one of my main goals is to answer via blog the questions I see everyday: "Why this doesn't work?", "My directive is not doing what I need", "My service is not updating"...

I think that the documentation itself needs to be done from various angles, and this is one for me.

I totally agree with you. That is one of the reasons I created this blog. I am 24/7 in #angularjs in freenode and I see questions repeated over and over again. My goal is to write about those solutions we give to them so they won't need to ask again.

On the other hand, my goal was to "sell" angular to the readers, not to scary them with $digest issues :)

Said that, I have in my TODO things about this matter.

Django for a backend will work good with any frontend framework (ember.js, angular.js, backbone.js, etc).

I think that none of the actual frontend frameworks will disappoint you. I just showed my opinion in one of them :)

Hello, I am the author of the post.

I think that there is a lot of comparison out there to create yet another one.

On the other hand, I don't have a deep knowledge of the competence to compare and I don't want to shot myself in the first post :P.

About the title, something can "rock" by its own.

Thank you for the comment :)