Why junior developers are learning bad habits from Angular

Post by looins » Thu, Jan 29, 2015, 2:50 PM UTC

kuni-toko-tachi wrote: post #9

The central problem with Angular is what is says about the software industry in general - that a framework so fundamentally and ridiculously flawed could invite such wide appeal suggests that many people have absolutely no idea what they are doing. The thousand monkeys approach to engineering has wide implications for security and safety of systems that we rely on. There is simply no way that you can say that you kno…

Post by delluminatus » Thu, Jan 29, 2015, 2:55 PM UTC

jere wrote: post #52

>Many would not even see the problem here, and just as children don't know cars can hurt, juniors don't know just how destructive this anti-pattern can be to performance, separation of concerns and long term code base maintenance. Yup, I don't get it. I guess not only am I eternally doomed to be a junior dev but also am being compared to a child, a monkey typing at a typewriter, but also someone who doesn't know JS a…

        $scope.displayName = function () {
            if ($scope.anonymous()) {
                return;
            }
            $scope.displayName = $scope.name;
        };

Post by crdoconnor » Thu, Jan 29, 2015, 2:58 PM UTC

bphogan wrote: post #69

jere wrote: post #52

>Many would not even see the problem here, and just as children don't know cars can hurt, juniors don't know just how destructive this anti-pattern can be to performance, separation of concerns and long term code base maintenance. Yup, I don't get it. I guess not only am I eternally doomed to be a junior dev but also am being compared to a child, a monkey typing at a typewriter, but also someone who doesn't know JS a…

This article only did one thing for me - demonstrate that the author himself doesn't understand Angular or the problems. I don't know Angular that well myself, but the author knew anything more than I did, he'd be able to spend the extra 30 seconds to write the refactored code. Dismiss this article. It's a waste of time and energy. In fact, I really shouldn't even be wasting my time commenting on it.

Post by yummybear » Thu, Jan 29, 2015, 2:58 PM UTC

eyko wrote: post #58

yummybear wrote: post #14

(sorry if this comes off a bit snarky) "Overuse of the eventing system ($watch, $emit, $broadcast) leading to performance problems and memory leaks and not realizing it or being able to debug it" Blindly overusing most features in frameworks or libraries can cause performance problems. Which memory leaks? "Writing Controllers and Directives that take dependencies which make them nearly impossible to test." Doesn't de…

"Blindly overusing most features in frameworks or libraries can cause performance problems. Which memory leaks?" Binding to event emitted by an object on another object, then deleting the receiver, can cause a memory leak if you don't unbind first.

Post by mcv » Thu, Jan 29, 2015, 3:00 PM UTC

jere wrote: post #52

>Many would not even see the problem here, and just as children don't know cars can hurt, juniors don't know just how destructive this anti-pattern can be to performance, separation of concerns and long term code base maintenance. Yup, I don't get it. I guess not only am I eternally doomed to be a junior dev but also am being compared to a child, a monkey typing at a typewriter, but also someone who doesn't know JS a…