[deleted]
AngularJS Cheat Sheet [pdf]
11–20 of 48 posts
Re: AngularJS Cheat Sheet [pdf]
#12Sadly will only be valid for ~6 months.
Re: AngularJS Cheat Sheet [pdf]
#1314 pages for a cheatsheet! The ones for emacs/vim are 1 page only, I guess we have a measure of the complication of angular now.
Give us a fn break, did you actually read the pdf? that's not a cheatsheet, more like collection of recipes.
> The ones for emacs/vim are 1 page only,
Apples and Oranges
> I guess we have a measure of the complication of angular now.
AngularJS isn't rocket science. But maybe we don't have the same definition complexity , which makes sense if you are a skiddie.
Re: AngularJS Cheat Sheet [pdf]
#14This looks like a good resource. But number 28 is wrong: > Always have a ‘.’ in your ng-models which insures prototypal inheritance. That isn't what that does. The egghead.io Angular videos also get this wrong. I really think that the vast majority of Angular programmers don't really understand how its scoping works. I've ranted about this before [1], it's just ridiculously complex. Some scopes inherit prototypically…
> Whatever the reason is for Angulars popularity, it isn’t that it’s a great framework.
Anything that makes programmers productive is a great tool. Angular 1.x definitely makes teams productive. It's one of the first web framework that comes with a specific testing framework. The clear separation between the DOM and the business logic makes apps more testable. And I could go for hours. Angular helps developers write complex apps faster and better.
Sure it isn't perfect, but show me something better with all the features AngularJs has.
AngularJS didn't became popular because it was from Google, a simple proof is the closure widget library nobody uses outside google. AngularJS became popular because it was obviously superior in term of developer experience.
Now your point about ng-model and scopes is valid.But it's not a angular problem, it's a javascript issue.Ultimately to understand angular you need to understand how javascript works, which many develpers don't.
Instead of saying "this thing is bad", Educate them. But I guess sensationalism drives more clicks.
Re: AngularJS Cheat Sheet [pdf]
#15I love working with angular, but the intense competition from other technologies combined with the overall negativity towards it has turned me off. The long term future of angular seems very uncertain.
Angular 2.0 is the New Coke of web development.
I suspect Google would gain a huge amount of goodwill if they backed down and announced: "You know, we'll rename the incompatible redesign as AngularNext 0.1 and use it to develop cutting-edge ideas. Then we'll bring the best of those into the mainstream Angular over time without breaking compatibility."
They could call the rebooted compatible Angular 2.0 "Harmony".
Re: AngularJS Cheat Sheet [pdf]
#16This looks like a good resource. But number 28 is wrong: > Always have a ‘.’ in your ng-models which insures prototypal inheritance. That isn't what that does. The egghead.io Angular videos also get this wrong. I really think that the vast majority of Angular programmers don't really understand how its scoping works. I've ranted about this before [1], it's just ridiculously complex. Some scopes inherit prototypically…
Some feedback; your article on angular is awful.
It's got some good information on some pieces of angular that more people should have a better understanding of, yes. However, trying to absorb that information through the shouting and sensational ranting is almost impossible.
This same article could have been written by a level-headed coder who understands the complexity of making a widely distributed browser frameworks and it would have been called "5 Angular Idiosyncrasies" or "Tricky Angular Patterns".
But no, sensationalism sells and loud, strident claims win the day. Why have humility and get less clicks when you can write a scathing takedown using strawman arguments and style yourself the next Crockford?
Your points are entirely valid criticisms, but your language and attitude make you sound like a blowhard trying to prove something or a shill promoting a competing framework with negative press.
Re: AngularJS Cheat Sheet [pdf]
#17This looks like a good resource. But number 28 is wrong: > Always have a ‘.’ in your ng-models which insures prototypal inheritance. That isn't what that does. The egghead.io Angular videos also get this wrong. I really think that the vast majority of Angular programmers don't really understand how its scoping works. I've ranted about this before [1], it's just ridiculously complex. Some scopes inherit prototypically…
> Whatever the reason is for Angulars popularity, it isn’t that it’s a great framework. Anything that makes programmers productive is a great tool. Angular 1.x definitely makes teams productive. It's one of the first web framework that comes with a specific testing framework. The clear separation between the DOM and the business logic makes apps more testable. And I could go for hours. Angular helps developers write…
I got tons of both hate and love for that blog post. One of the few criticisms that I can accept is the "The problems are real, but don't matter that much." view. I don't agree, but I suppose people can have different experiences there.
Any 'sensationalism' comes from legitimate anger with the framework, after having spent over a year working with it on a large project.
> Now your point about ng-model and scopes is valid.But it's not a angular problem, it's a javascript issue.
This I don't agree with. Yes, JavaScript has prototypical inheritance between objects, but certainly not between scopes. It has lexical scoping like everyone else. The decision to have scopes be objects that (sometimes, not always) inherit from one another, is entirely on Angular. So is the decision to have ng-model silently create objects on this scope.
Re: AngularJS Cheat Sheet [pdf]
#18Sadly will only be valid for ~6 months.
What's happening in 6 months? Is my angular code going to spoil?
Re: AngularJS Cheat Sheet [pdf]
#19This looks like a good resource. But number 28 is wrong: > Always have a ‘.’ in your ng-models which insures prototypal inheritance. That isn't what that does. The egghead.io Angular videos also get this wrong. I really think that the vast majority of Angular programmers don't really understand how its scoping works. I've ranted about this before [1], it's just ridiculously complex. Some scopes inherit prototypically…
> Whatever the reason is for Angulars popularity, it isn’t that it’s a great framework. Anything that makes programmers productive is a great tool. Angular 1.x definitely makes teams productive. It's one of the first web framework that comes with a specific testing framework. The clear separation between the DOM and the business logic makes apps more testable. And I could go for hours. Angular helps developers write…
> It's one of the first web framework that comes with a specific testing framework.
Where on earth did you get that idea?
> AngularJS didn't became popular because it was from Google
But it was definitely helped that it was so heavily promoted by Google
> your point about ng-model and scopes is valid. But it's not a angular problem, it's a javascript issue
Again...what? JavaScript doesn't have `ng-model`...Angular does. It's an Angular problem through and through.