xonecasacenox

Thank you for this very political correct answer. I'll make sure to take you up on your offer to contribute as best as I can, meanwhile can you take a look at our pull request? https://github.com/angular/builtwith.angularjs.org/pull/242

xD (For clarity I'm attempting to be funny in this comment)

I agree with you that the structure is still up to the developer, but if you get too creative you'll end up in a mess of code. In this thread other organization approaches have been suggested, that are in my opinion better than the angular seed suggestion. The point I try to make is that Angular when compared to other existing options is more structured. How do you find the balance between flexibility and structure depends on your team and project.

After you wrote about my example, I realize that you are correct, it was not a great one. My bad!

Wow, this is great. Thank you for sharing this with me!

I can understand why you'd think of me as a Angular diehard, but I'm not. I try to choose the best tool for the job, and because of it's structure Angular was the best choice for this project. If Ember or Backbone had been more suited I would just as easily had a love affair with them too!

As for your bad experience, I can see how that can happen with Angular, but I can also see that happening in other ways with other libraries. In my opinion that is solved by using good code patterns and writing code for others, not for yourself. I'll leave this relevant quote:

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live." - Martin Golding

You make good points, and I'll try to explain myself as best as I can. (I'm Sean, I wrote this article).

String templates outperform DOM, this was very true in the past and as far as I know still is true. The great advantage of it, is the "live" data bindings, which I think depend on the template being the actual live DOM. (I can be wrong here, and if I am then I need to go learn more about this choice)

As for the documentation point, you are right I contradict myself. What I meant to say is that angular suggests a way to structure your application versus backbone for example that only gives you the tools and no structure.

Thanks for pointing these out, I'll have to be more careful on how I express myself next time I write something.