Why am I just noticing the "by Google" under the logo?!
Diving into AngularJS
11–20 of 48 posts
Re: Diving into AngularJS
#12Am I the only one who dismissed AngularJS by the fact that they use a nearly unmodified bootstrap design?
Re: Diving into AngularJS
#13So many client side js libraries. Can anybody help compare Ember, Meteor, Angular and Backbone?
came up a few days ago - http://sporto.github.io/blog/2013/04/12/comparison-angular-b...
Re: Diving into AngularJS
#14Why am I just noticing the "by Google" under the logo?!
[deleted]
Re: Diving into AngularJS
#15I tend to dive a lot into a source code when I am working with a library. You always have missing spots in documentation but you can actually know what's going on by reading the code. This is one of the reasons I am super comfortable with Backbone. However I cannot comprehend Angular's source code on github. Can anyone give me pointers on where to start reading it and/or how it's organized?
I did start diving into angular source code, and found it quite readable. I simply read it from top to bottom, and it is quite well understandable this way. I read it one function at a time on my ipad whenever i needed a break, and i think one could manage to read it all in one or two weeks (depending on how much free time in the week you've got)
Re: Diving into AngularJS
#16Am I the only one who dismissed AngularJS by the fact that they use a nearly unmodified bootstrap design?
Probably, as that doesn't seem like a good reason.
Re: Diving into AngularJS
#17I tend to dive a lot into a source code when I am working with a library. You always have missing spots in documentation but you can actually know what's going on by reading the code. This is one of the reasons I am super comfortable with Backbone. However I cannot comprehend Angular's source code on github. Can anyone give me pointers on where to start reading it and/or how it's organized?
I found AngularJS very readable and was able to read it during my commute over the course of a week.
However: I read the documentation first.
I think you'll find if you give it a chance, you'll find that AngularJS has excellent documentation.
Someone put a lot of effort into taking what is organised for implementation (code) and reorganising it for users, and it was something that was very much appreciated.
For example, you should look at this:
* http://docs.angularjs.org/guide/di
There's a very subtle piece in there about how AngularJS figures out what the dependencies of a function actually are, and understanding that piece is key to understanding how much of the AngularJS code is written.
Re: Diving into AngularJS
#18Why am I just noticing the "by Google" under the logo?!
Google staffs the project with several talented engineers. Misko Hevery is an amazing benevolent dictator. He earns my trust and respect. A confluence of genius and pragmatism.
Re: Diving into AngularJS
#19So many client side js libraries. Can anybody help compare Ember, Meteor, Angular and Backbone?
Take a look at ToDoMVC: http://todomvc.com/
"TodoMVC [is] a project which offers the same Todo application implemented using MV* concepts in most of the popular JavaScript MV* frameworks of today."
Re: Diving into AngularJS
#20Am I the only one who dismissed AngularJS by the fact that they use a nearly unmodified bootstrap design?
Probably, as that doesn't seem like a good reason.
Quite. But how much effort they put in their website and documentation is somehow important to me. Then again, Ruby projects always look glamorous while Haskell projects (just an example for an exotic language) look like some HTML document someone wrote 10 years ago on an university computer.
Ember.js in comparison has a certain glow to it. Especially with that weird mascot.