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

I won't be using Angular for my next project and neither should you

javascriptkicks.com

Post reply on HN
Print view View original

11–20 of 22 posts

Re: I won't be using Angular for my next project and neither should you

#11

Post by mmilano »

The Sharepoint experience comparison is pretty pointless. The complaint is that he's being consulted to fix things un-qualified people broke. Sounds like, consulting.

I haven't put food on the table with Sharepoint consulting, but "broken installations" can be done via the GUI by employees with admin access right? ... where breaking AngularJS apps would be done by those with access to the code. Very different.

Then what type of consulting doesn't feel like selling your soul when you've achieved a significant level of expertise in an area?

Pretty dramatic, but interesting bits none the less.

Re: I won't be using Angular for my next project and neither should you

#12

Post by artjumble »

ufo wrote: post #7

Is it really true that the order you write html attributes/directives in angular matters? That was pretty surprising for me.

After looking at the linked article and reading the comments, it appears that it doesn't make an actual impact on performance. He is just suggesting the ordering for consistency.

Re: I won't be using Angular for my next project and neither should you

#13

Post by artjumble »

craigching wrote: post #9
gnrlbzik wrote: post #2

I must say my gut reaction to such titles is usually rejection of premiss. But I must say article is well written and on point. Time will tell.

Personally I would have liked more concrete examples of the problem he's outlined. For instance, his assertion that it teaches junior programmers bad habits. Like what? I'm not sure that's been my experience, but I'm a seasoned JavaScript developer and understand what's going on under the covers. I really would like to better understand that if I use Angular and expose it to my junior programmers, what problems am I…

Agreed. It is hard to just accept these viewpoints without backing them up with some examples or data.

The v2 opinion and comparison to SharePoint just sounds mostly like FUD.

The comments about junior devs and masquerading as javascript I just don't buy. Sure someone new to programming might be able to just throw something together and not learn, but someone attempting to learn will still learn a lot using Angular.

Re: I won't be using Angular for my next project and neither should you

#15

Post by gnrlbzik »

craigching wrote: post #9
gnrlbzik wrote: post #2

I must say my gut reaction to such titles is usually rejection of premiss. But I must say article is well written and on point. Time will tell.

Personally I would have liked more concrete examples of the problem he's outlined. For instance, his assertion that it teaches junior programmers bad habits. Like what? I'm not sure that's been my experience, but I'm a seasoned JavaScript developer and understand what's going on under the covers. I really would like to better understand that if I use Angular and expose it to my junior programmers, what problems am I…

Do agree with you on that. My use of "on point" is probably too strong for this article. Better would be mostly on point. Examples are missing. And does feel more like fud when certain points are discussed.

Re: I won't be using Angular for my next project and neither should you

#16

Post by gnrlbzik »

artjumble wrote: post #13
craigching wrote: post #9

Earlier quoted context omitted.

Personally I would have liked more concrete examples of the problem he's outlined. For instance, his assertion that it teaches junior programmers bad habits. Like what? I'm not sure that's been my experience, but I'm a seasoned JavaScript developer and understand what's going on under the covers. I really would like to better understand that if I use Angular and expose it to my junior programmers, what problems am I…

Agreed. It is hard to just accept these viewpoints without backing them up with some examples or data. The v2 opinion and comparison to SharePoint just sounds mostly like FUD. The comments about junior devs and masquerading as javascript I just don't buy. Sure someone new to programming might be able to just throw something together and not learn, but someone attempting to learn will still learn a lot using Angular.

Well I can relate to notion. Not to the exact manner. But when I had a small team and we worked on app, about 2.5 years ago. I would say that general premise was in regards of PRs that i have reviewed, is that more junior devs, would over populated logic in templates and in general just do little bit of extra code in places where it should of not existed. That said, I think it is applicable to any junior developer, when documentation is a bit convoluted. I can't say that Angular has the best documentation and has no ramp up time to get on board with it, if anything it has longer ramp up time. Especially if you start from scratch as a team.

Re: I won't be using Angular for my next project and neither should you

#18

Post by craigching »

gnrlbzik wrote: post #16
artjumble wrote: post #13

Earlier quoted context omitted.

Agreed. It is hard to just accept these viewpoints without backing them up with some examples or data. The v2 opinion and comparison to SharePoint just sounds mostly like FUD. The comments about junior devs and masquerading as javascript I just don't buy. Sure someone new to programming might be able to just throw something together and not learn, but someone attempting to learn will still learn a lot using Angular.

Well I can relate to notion. Not to the exact manner. But when I had a small team and we worked on app, about 2.5 years ago. I would say that general premise was in regards of PRs that i have reviewed, is that more junior devs, would over populated logic in templates and in general just do little bit of extra code in places where it should of not existed. That said, I think it is applicable to any junior developer, w…

Thank you, that example makes sense. You see, as an experienced developer I would never think to intertwine my logic into my templates, so it's hard to envision what a junior developer might do.

Re: I won't be using Angular for my next project and neither should you

#19

Post by robertthegrey »

gnrlbzik wrote: post #16
artjumble wrote: post #13

Earlier quoted context omitted.

Agreed. It is hard to just accept these viewpoints without backing them up with some examples or data. The v2 opinion and comparison to SharePoint just sounds mostly like FUD. The comments about junior devs and masquerading as javascript I just don't buy. Sure someone new to programming might be able to just throw something together and not learn, but someone attempting to learn will still learn a lot using Angular.

Well I can relate to notion. Not to the exact manner. But when I had a small team and we worked on app, about 2.5 years ago. I would say that general premise was in regards of PRs that i have reviewed, is that more junior devs, would over populated logic in templates and in general just do little bit of extra code in places where it should of not existed. That said, I think it is applicable to any junior developer, w…

You've hit the nail on the head, but I honestly don't know why more senior developers can't see it - unless they don't actually work with juniors on a regular basis? Anyway, due to all the cries about FUD on the topic of juniors specifically, I decided it needs its own writeup - you can find it here if you want more clarification: https://news.ycombinator.com/item?id=8965935

Re: I won't be using Angular for my next project and neither should you

#20

Post by robertthegrey »

artjumble wrote: post #12
ufo wrote: post #7

Is it really true that the order you write html attributes/directives in angular matters? That was pretty surprising for me.

After looking at the linked article and reading the comments, it appears that it doesn't make an actual impact on performance. He is just suggesting the ordering for consistency.

I don't know how you can say that when in his article he clearly says:

"In AngularJS, not all HTML attributes are equal; some have no significant effect; others have a profound impact on how your page is rendered."

If it was just about consistency, then it would for part of an Angular style guide that so many companies produce.

Post reply on HN