If anybody is having issues loading the page, here's a really long screenshot of the text... http://milankragujevic.com/uploads/2015-01-29_151409.jpg
Sorry but I got an "Error 1011, access denied"
Why junior developers are learning bad habits from Angular
31–40 of 138 posts
Re: Why junior developers are learning bad habits from Angular
#32The 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.
http://i.imgur.com/VibuzuV.png
Cool page, bro. I guess you don't really want people to read it.
Re: Why junior developers are learning bad habits from Angular
#33Earlier quoted context omitted.
Settling for JS in the first place says something about the software industry in general. Let alone any MVC frameworks-of-day.
You say that as if there is some volition involved in the "settling" on JS. But there is no cohesive group with the agency to do any such thing. It's like blaming human evolution on individual human choices throughout history.
Well, we could decide as an industry that we really need to fix the code-in-web-browsers problem, and then fix it with a language which encourages safety and reliability. The fact that we haven't done that supports the OP's point.
Re: Why junior developers are learning bad habits from Angular
#34The 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…
Settling for JS in the first place says something about the software industry in general. Let alone any MVC frameworks-of-day.
If that were true there would be no such things as CoffeeScript and TypeScript. The market settled on JavaScript, not the software industry. The software industry is doing what it can with the hand the market dealt them. It's not like x86 is an awesome architecture, but here we are.
Re: Why junior developers are learning bad habits from Angular
#35Re: Why junior developers are learning bad habits from Angular
#36It seems like what junior Angular devs really need is a post showing examples of both what NOT to do and also what to do INSTEAD.
I think the difficulty of Angular is largely you have so many tools available but it's hard for a junior developer (like myself) to recognise when each should be used.
Re: Why junior developers are learning bad habits from Angular
#37The 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…
This is a rather surprisingly and unnecessary harsh comment. Would you like to explain why do you think Angular is so flawed?
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 JavaScript. The knowledge learned from it is hardly transferable to the next framework down the line.
To me it looks a lot like SOAP. Everybody is acting like they understand what is going on. But nobody really does.
Re: Why junior developers are learning bad habits from Angular
#38The 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…
Angular brutally sucks in a variety of ways, but security isn't one of them [pentester].
Specifically, the builtin "stuff" makes it actively hard to XSS, and in SPAs that's job #1.
Re: Why junior developers are learning bad habits from Angular
#39The 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…
Settling for JS in the first place says something about the software industry in general. Let alone any MVC frameworks-of-day.
But what does it say exactly? That people prefer C-like syntax as opposed to anything else? That "done is better than perfect" when it comes to releasing a new language? That Netscape got it "wrong" in the 90's by including Javascript in their browser? I'm not quite sure what you're implying here.
Re: Why junior developers are learning bad habits from Angular
#40Earlier quoted context omitted.
Thats a little hyperbole. I "support" it in that its an easy way for someone to make a typical web application without having to know the details of call vs apply, arguments, prototypes, etc, or writing a lot of boilerplate. So in that way I guess angular is for people who don't want to learn "javascript" - and thats what you see it being used for generally anyways.
And how do those developers deal with issues such as XSS, injection, untrusted JSON, etc if they don't know JavaScript? I agree with the OP. At some point it will come back to bite you. I've watched many ASP and ASP.NET developers struggle with more modern web methodologies such as restful web apis, client side MVC, etc and it's because they never took the time to understand the web, the browser, or javascript and le…
>And how do those developers deal with issues such as XSS, injection, untrusted JSON, etc if they don't know JavaScript? I agree with the OP. At some point it will come back to bite you.
Well thats the thing, they don't because thats what the senior devs are for, and learning that stuff is part of becoming a senior dev. I just don't see angular making any more developers who don't really know the core of their technology than any other "generation"... I bet the exact same things were said about jQuery 8 years ago.