I won't be using Angular for my next project and neither should you
javascriptkicks.com
I won't be using Angular for my next project and neither should you
1–10 of 22 posts
Re: I won't be using Angular for my next project and neither should you
#2I 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.
Re: I won't be using Angular for my next project and neither should you
#3Yep. Robert's a crack dev and I found his insights on the issues with Angular spot on.
Re: I won't be using Angular for my next project and neither should you
#4Clicking the back button after going to this article prevents you from returning to HN, but rather sends you to jskicks' front page and re-opens the article.
Really shitty behavior. Or is this supposed to work better on mobile?
Re: I won't be using Angular for my next project and neither should you
#5Clicking the back button after going to this article prevents you from returning to HN, but rather sends you to jskicks' front page and re-opens the article. Really shitty behavior. Or is this supposed to work better on mobile?
Actually completely unreadable on mobile
Re: I won't be using Angular for my next project and neither should you
#6Clicking the back button after going to this article prevents you from returning to HN, but rather sends you to jskicks' front page and re-opens the article. Really shitty behavior. Or is this supposed to work better on mobile?
For me, it just keeps taking me back to the same article.
Re: I won't be using Angular for my next project and neither should you
#7Is it really true that the order you write html attributes/directives in angular matters? That was pretty surprising for me.
Re: I won't be using Angular for my next project and neither should you
#8Clicking the back button after going to this article prevents you from returning to HN, but rather sends you to jskicks' front page and re-opens the article. Really shitty behavior. Or is this supposed to work better on mobile?
Good feedback - something I'll look at getting fixed asap
Re: I won't be using Angular for my next project and neither should you
#9I 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 likely to encounter so that I can counter them? That would have made this article much more useful to me. It appears to be just a screed without any concrete examples.
Re: I won't be using Angular for my next project and neither should you
#10Clicking the back button after going to this article prevents you from returning to HN, but rather sends you to jskicks' front page and re-opens the article. Really shitty behavior. Or is this supposed to work better on mobile?
Not only is it hard to read on mobile, it also somehow disables inertia scrolling, something I've never experienced on an angularjs site