>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…
Why junior developers are learning bad habits from Angular
61–70 of 138 posts
Re: Why junior developers are learning bad habits from Angular
#62Earlier quoted context omitted.
For one, it is incompatible with the whole open web stack. You cannot use Bootstrap with it. And if you decide to move off Angular, you are going to be in a world of pain. Second and worst of all - it is a monolithic framework. As long as you just do things the "Angular Way" - you are fine. If you want to change or override something, you are in a world of pain. If you are learning Angular - you are hardly learning J…
1: You shouldn't be using bootstrap, even though you can with angular. 2: What do you need to do in the front end that can't be accomplished the 'angular way'? I'm not sure you understand what monolithic really means. The beauty part of angular is that you can use it as little or as much as you'd like in your web applications. 3: Angular 2 is going to be preeeetty much only ecma6. Also, understanding angular means yo…
Why in the world would you say that
Re: Why junior developers are learning bad habits from Angular
#63Re: Why junior developers are learning bad habits from Angular
#64Re: Why junior developers are learning bad habits from Angular
#65Re: Why junior developers are learning bad habits from Angular
#66Anyone has an exemple on how to use the $scope properly ...? He only shows the wrong way of using it, but has no code for the right way.
Don't blame the tool blame the fool :).
Re: Why junior developers are learning bad habits from Angular
#67Earlier quoted context omitted.
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. I have yet to see an Angular project that doesn't qualify as tiny . For that purpose -- banging out some internal CRUDish app -- if it allows people to create working succ…
> trying to abstract Javascript into some sort of classic OOP language Which is wrong. And, I think, stems from the way CS is taught. Everyone starts with Java and learns that programming is all about knowing that a dog and a cat are just subclasses of the 4-legged-creature class, which is itself inherited from the mammal class. Wait no, that's not right now is it? But it's how people learn. JavaScript is a beautiful…
I had the pleasure to learn about Pascal, C, C++, Smalltalk, Caml Light, Prolog, Algol, PL/SQL and Java, as well as, their respective paradigms.
Re: Why junior developers are learning bad habits from Angular
#68The 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…
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. I have yet to see an Angular project that doesn't qualify as tiny . For that purpose -- banging out some internal CRUDish app -- if it allows people to create working succ…
JavaScript uses prototype inheritance and can fake classical inheritance, but it has its limitations.
Re: Why junior developers are learning bad habits from Angular
#69>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…
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.
Re: Why junior developers are learning bad habits from Angular
#70The page is not loading properly for me (on a Windows laptop with Chrome). When I use the given link I get "500 - InternalServerError Something went horribly, horribly wrong while servicing your request. We're sorry :-(" and when I go via javascriptkicks.com it keeps loading and never completes.