Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AngularJS Cheat Sheet [pdf]

dncmagazine.blob.core.windows.net

Post reply on HN
Print view View original

21–30 of 48 posts

Re: AngularJS Cheat Sheet [pdf]

#21

Post by lars »

gooseus wrote: post #16
lars wrote: post #9

This 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 framewo…

FWIW, my tone in that article is exactly the tone I would have if you got me started on this in a real life conversation. If I sound like a blowhard, at least I'm an authentic blowhard, it's not some act I put on for the clicks.

The tone comes from being legitimately angry at these flaws in Angular, but also from having to discover them myself, instead of reading about them on someone else's blog. The various JavaScript frameworks affect hundreds of thousands of developers every day, and choosing the wrong one can cost companies a lot of money. I really think that as a profession we'd make progress faster if more people wrote angry blog posts about things that are bad.

Re: AngularJS Cheat Sheet [pdf]

#23

Post by Bahamut »

pavlov wrote: post #15
mberning wrote: post #10

I 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".

The Angular team is not going to do backwards compatibility with Angular 1.x with 2.0 at all - they're going to help with migration some with the router, but the api are fully incompatible.

FWIW, Angular 2 is awesome to work with, even in its alpha form. Productivity with it should be immensely improved compared to 1.x.

Re: AngularJS Cheat Sheet [pdf]

#25

Post by aikah »

ryannevius wrote: post #19
aikah wrote: post #14

Earlier quoted context omitted.

> 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 do…

> Where on earth did you get that idea?

Well you didn't disprove my assertion (I was obviously talking about front end frameworks) by citing a front end framework that came with an extensive testing framework. So why on earth are you saying something without backing it with facts?

> But it was definitely helped that it was so heavily promoted by Google

I started using AngularJS in 2011 it had 0 promotion from Google. It wasn't even a Google product at that time.

> Again...what? JavaScript doesn't have `ng-model`...Angular does. It's an Angular problem through and through.

No the problem is that Javascript doesn't have pointer variables,therefore when using variables in a scope you need to use object properties and not objects directly if you want to refer to it in the outer scope. It has nothing to do with angular but everything to do with the way Javascript works.

Re: AngularJS Cheat Sheet [pdf]

#26

Post by chvid »

lars wrote: post #21
gooseus wrote: post #16

Earlier quoted context omitted.

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 framewo…

FWIW, my tone in that article is exactly the tone I would have if you got me started on this in a real life conversation. If I sound like a blowhard, at least I'm an authentic blowhard, it's not some act I put on for the clicks. The tone comes from being legitimately angry at these flaws in Angular, but also from having to discover them myself, instead of reading about them on someone else's blog. The various JavaScr…

Your article is solid and I am grateful that you wrote it.

And I understand your tone completely.

When a framework is oversold in a major way those who try to use it on real life projects get very frustrated.

Re: AngularJS Cheat Sheet [pdf]

#27

Post by chrislgrigg »

lars wrote: post #21
gooseus wrote: post #16

Earlier quoted context omitted.

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 framewo…

FWIW, my tone in that article is exactly the tone I would have if you got me started on this in a real life conversation. If I sound like a blowhard, at least I'm an authentic blowhard, it's not some act I put on for the clicks. The tone comes from being legitimately angry at these flaws in Angular, but also from having to discover them myself, instead of reading about them on someone else's blog. The various JavaScr…

I appreciate a human, conversational approach to technical information and applaud you for your blog's tone. If you were writing for a professional news site it might be inappropriate but as a post on your own blog, you're entitled to whatever writing style you want.

Re: AngularJS Cheat Sheet [pdf]

#28

Post by Too »

> 24. Wherever possible, use AngularJS versions of JavaScript functionality. So instead of setInterval, use the $interval service....It becomes easier to mock them or write unit tests

I've always been very against these angular versions of basic js functions because it requires everyone on the team to learn them and it puts you even deeper into the angular lock in swamp, hindering you from eventually changing your view-framework in the future. Any takes on this?

I like the data binding of angular but try to restrict angular coming in contact with "core" code. As example we hardly write any services, we just use them to hold an instance of plain js-classes that can easily be reused in non angular projects.

Re: AngularJS Cheat Sheet [pdf]

#29

Post by Bahamut »

Too wrote: post #28

> 24. Wherever possible, use AngularJS versions of JavaScript functionality. So instead of setInterval, use the $interval service....It becomes easier to mock them or write unit tests I've always been very against these angular versions of basic js functions because it requires everyone on the team to learn them and it puts you even deeper into the angular lock in swamp, hindering you from eventually changing your vi…

Services such as $interval or $timeout are very simple - $http is also a fairly simple service to replace too. I don't really view it as much of an issue when it comes to lock in or migration, there are usually far more perilous pitfalls when it comes to lack of being able to migrate, such as bad app architecture or hacks.
Post reply on HN