6 ms·

Guys, relax and stop whining. You are probably wrong about what is going to happen with Angular, because you underestimate how massive Angular has become. I re

Guys, relax and stop whining. You are probably wrong about what is going to happen with Angular, because you underestimate how massive Angular has become. I recently began searching for a new JavaScript job. I don't like Angular at all and I am skipping all positions that mention it. I have to skip ~90% of all ads. Think of it – 90% of companies that are expanding their web development use Angular. So, even if this change will kill Angular, it will probably take years. It has become too big to fail. If you like Angular, get excited about it. Look at how .NET or Java guys accept everything coming from Microsoft or Oracle. You are in a similar ship now. No one got fired for choosing Angular. No one will.

colinramsay 12y ago
Is this right? I can't believe for a millisecond that 90% of all new JS jobs relate to Angular, it's a horrible and overblown framework with a high barrier to entry. Were you looking at a particular subset of jobs, a particular industry or in a particular location?
- ggregoire 12y ago
  > it's a horrible and overblown framework with a high barrier to entry Actually if you have several years of experience in programming and a good knowledge of JavaScript and classical design patterns like observer and singleton, it's not that hard. Angular is to build web applications, it's necessary more complicated to use than jQuery whose purpose is to build web pages.
- ycitm 12y ago
  I've just been looking for JavaScript work in the UK. Certainly the majority (maybe not 90%, but definitely > 50%) of jobs mention Angular. It's difficult to tell how many of these are just "put something cool on the advert to attract the hipsters" and how many are actual "we use or will use angular heavily in production" though.
  - bshimmin 12y ago
    UK here too, and this sounds about right. I would say that most of these shops are not using Angular "heavily in production" right now - either they will have some portion of an existing project that they're trying to move to Angular or a greenfield project for which they're evaluating Angular and think anybody with that skill would be a valuable addition to the team, whether or not they end up using Angular. In terms of roles I see posted on LinkedIn in the UK (which may or may not be representative of the industry as a whole, but it's all I've got to go on), there's a lot of Angular, a lot of "Angular or similar (eg. Backbone)", and a lot of "MVC (eg. Angular, Backbone)". Many of those same roles do also mention jQuery, but not with the same sort of billing it might have had two years ago. I'm not sure I've ever seen a role specifically mentioning Ember. Like quite a few others in this thread, I'm an Angular naysayer for the standard reasons, and would generally prefer to avoid it, but the market does rather dictate what we end up doing sometimes, for better or for worse.
- Jgrubb 12y ago
  > it's a horrible and overblown framework with a high barrier to entry Listen, if I can figure it out and get lots and lots of work done with it, it's neither horrible nor overblown and the barrier of entry was there but I got over it. By all means, keep ignoring it, but drop the shtick where you know better than thousands and thousands of us out here building things with it.
  - colinramsay 12y ago
    I'm not ignoring it, please don't put words in my mouth. If people want to use it then that's their choice, albeit one I find fairly baffling. Given the other replies to my comment it seems I'm not alone.
  - kuni-toko-tachi 12y ago
    Hey pal, drop the chip on your shoulder. Just because AngularJS has wide adoption doesn't change the fact that it is an extremely poorly designed framework. I also refuse to consider AngularJS jobs. Many developers have had to suffer through bad frameworks like GWT because of industry trends. Those bruises are not badges of honor. ReactJS is a framework that is clearly better designed. Why waste time learning and suffering through AngularJS absurdities when ReactJS exists?
    - mgkimsal 12y ago
      ... because jobs? I'm in agreement with your point, but... if 'the market' wants angular... 'the market' is going to have a hell of a time dealing with a mess in a couple of years when many of the decision makers that mandated angular move on to something else and leave piles of mess behind for someone else to clean up.
      - emilis_info 12y ago
        There may not be moving on. Or it may take a very long time. Angular is that big already. Previously there was no the framework for web frontend development (like Rails for Ruby). From now on you will need convincing reasons to use anything else, even if it is clearly better. Moving on to something else will be much harder.
- gloverkcn 12y ago
  I've been looking In the US for remote positions, contracts, and local. If they are using a framework theres 90% chance it's angular. For all javascript/html/Css type jobs its more like 50-60%. I've talked to consulting/contracting companies and they have agreed that they have far more requests angular than any other front end tech. I agree with your comment about it. I tried it and didn't like it. I've talked to a few devs who Have mentioned issue in larger projects more around organizing the code base.). Regardless of all of that. There's so much demand that I'm going to drop emberjs and learn angular.
- pavlov 12y ago
  Angular is attractive to "strategic technologists" because it's rich in ceremony, edifice and nomenclature inspired by the European Union. A platform like this achieves critical mass when it starts appearing in McKinsey slides, and then it will become a permanent fixture in job ads for the next 10 years. I guess Angular has reached that milestone.
  - fetbaffe 12y ago
    The enterprise folks have arrived to ruin everything. Run, just run!
- emilis_info 12y ago
  Yes it is a horrible and overblown framework. However it has this "made by Google" sticker on it. No one got fired for choosing Google ;) I haven't done the exact numbers and 90% seems really high, but it feels like it. I bet the exact number wouldn't be lower than 75%. I live in Eastern Europe, but I am mostly looking for remote jobs. I am a real full-stack developer and would gladly work on backend with Node.js, but these jobs are even rarer these days.
  - fungi 12y ago
    > No one got fired for choosing Google ;) Only a brave woman would build her house on GWT
- cloverich 12y ago
  > it's a horrible and overblown framework with a high barrier to entry. I'm honestly surprised how often I keep hearing about its high barrier to entry. I've worked on ~5 different MVC style web frameworks, all server side, over ~5 years of professional programming. I just started a front-end position using Angular for the last three months, and have found it pretty straight-forward to pick up. That is, the concepts I learned server-side have translated fairly cleanly to the front-end. Most of the people I've seen struggle with the framework so far are those that didn't have that server side experience. Which isn't to say its required, but only to say some of the concepts they struggle the most with are concepts you need for any MVC style web framework - server side or front-end. Its not that they are that similar, but that they encounter and solve many of the same problems. Routing, separation of concerns, dependency injection, testing, getting what you want into the template, etc. And Angular isn't what you'd call a micro framework (see Django vs Flask or Bottle from Python world, for example). So of course Angular is large; it tries to solve alot of problems for you (how well it does so is another story). Anyways, the take-away (from my point of view) is that much of the work that used to be done by server-side guys can now be done by front-end guys. So they have to learn all the same concepts and struggle with all the same problems to be effective.
- Ronsenshi 12y ago
  90% is certainly high. But he's not that far from the truth. A lot of companies do expect anyone working with JS to know Angular... which is not good for me. I'm really not a fan of that framework.

colinramsay 12y ago

Is this right? I can't believe for a millisecond that 90% of all new JS jobs relate to Angular, it's a horrible and overblown framework with a high barrier to entry. Were you looking at a particular subset of jobs, a particular industry or in a particular location?

ggregoire 12y ago
> it's a horrible and overblown framework with a high barrier to entry Actually if you have several years of experience in programming and a good knowledge of JavaScript and classical design patterns like observer and singleton, it's not that hard. Angular is to build web applications, it's necessary more complicated to use than jQuery whose purpose is to build web pages.
ycitm 12y ago
I've just been looking for JavaScript work in the UK. Certainly the majority (maybe not 90%, but definitely > 50%) of jobs mention Angular. It's difficult to tell how many of these are just "put something cool on the advert to attract the hipsters" and how many are actual "we use or will use angular heavily in production" though.
- bshimmin 12y ago
  UK here too, and this sounds about right. I would say that most of these shops are not using Angular "heavily in production" right now - either they will have some portion of an existing project that they're trying to move to Angular or a greenfield project for which they're evaluating Angular and think anybody with that skill would be a valuable addition to the team, whether or not they end up using Angular. In terms of roles I see posted on LinkedIn in the UK (which may or may not be representative of the industry as a whole, but it's all I've got to go on), there's a lot of Angular, a lot of "Angular or similar (eg. Backbone)", and a lot of "MVC (eg. Angular, Backbone)". Many of those same roles do also mention jQuery, but not with the same sort of billing it might have had two years ago. I'm not sure I've ever seen a role specifically mentioning Ember. Like quite a few others in this thread, I'm an Angular naysayer for the standard reasons, and would generally prefer to avoid it, but the market does rather dictate what we end up doing sometimes, for better or for worse.
Jgrubb 12y ago
> it's a horrible and overblown framework with a high barrier to entry Listen, if I can figure it out and get lots and lots of work done with it, it's neither horrible nor overblown and the barrier of entry was there but I got over it. By all means, keep ignoring it, but drop the shtick where you know better than thousands and thousands of us out here building things with it.
- colinramsay 12y ago
  I'm not ignoring it, please don't put words in my mouth. If people want to use it then that's their choice, albeit one I find fairly baffling. Given the other replies to my comment it seems I'm not alone.
- kuni-toko-tachi 12y ago
  Hey pal, drop the chip on your shoulder. Just because AngularJS has wide adoption doesn't change the fact that it is an extremely poorly designed framework. I also refuse to consider AngularJS jobs. Many developers have had to suffer through bad frameworks like GWT because of industry trends. Those bruises are not badges of honor. ReactJS is a framework that is clearly better designed. Why waste time learning and suffering through AngularJS absurdities when ReactJS exists?
  - mgkimsal 12y ago
    ... because jobs? I'm in agreement with your point, but... if 'the market' wants angular... 'the market' is going to have a hell of a time dealing with a mess in a couple of years when many of the decision makers that mandated angular move on to something else and leave piles of mess behind for someone else to clean up.
    - emilis_info 12y ago
      There may not be moving on. Or it may take a very long time. Angular is that big already. Previously there was no the framework for web frontend development (like Rails for Ruby). From now on you will need convincing reasons to use anything else, even if it is clearly better. Moving on to something else will be much harder.
gloverkcn 12y ago
I've been looking In the US for remote positions, contracts, and local. If they are using a framework theres 90% chance it's angular. For all javascript/html/Css type jobs its more like 50-60%. I've talked to consulting/contracting companies and they have agreed that they have far more requests angular than any other front end tech. I agree with your comment about it. I tried it and didn't like it. I've talked to a few devs who Have mentioned issue in larger projects more around organizing the code base.). Regardless of all of that. There's so much demand that I'm going to drop emberjs and learn angular.
pavlov 12y ago
Angular is attractive to "strategic technologists" because it's rich in ceremony, edifice and nomenclature inspired by the European Union. A platform like this achieves critical mass when it starts appearing in McKinsey slides, and then it will become a permanent fixture in job ads for the next 10 years. I guess Angular has reached that milestone.
- fetbaffe 12y ago
  The enterprise folks have arrived to ruin everything. Run, just run!
emilis_info 12y ago
Yes it is a horrible and overblown framework. However it has this "made by Google" sticker on it. No one got fired for choosing Google ;) I haven't done the exact numbers and 90% seems really high, but it feels like it. I bet the exact number wouldn't be lower than 75%. I live in Eastern Europe, but I am mostly looking for remote jobs. I am a real full-stack developer and would gladly work on backend with Node.js, but these jobs are even rarer these days.
- fungi 12y ago
  > No one got fired for choosing Google ;) Only a brave woman would build her house on GWT
cloverich 12y ago
> it's a horrible and overblown framework with a high barrier to entry. I'm honestly surprised how often I keep hearing about its high barrier to entry. I've worked on ~5 different MVC style web frameworks, all server side, over ~5 years of professional programming. I just started a front-end position using Angular for the last three months, and have found it pretty straight-forward to pick up. That is, the concepts I learned server-side have translated fairly cleanly to the front-end. Most of the people I've seen struggle with the framework so far are those that didn't have that server side experience. Which isn't to say its required, but only to say some of the concepts they struggle the most with are concepts you need for any MVC style web framework - server side or front-end. Its not that they are that similar, but that they encounter and solve many of the same problems. Routing, separation of concerns, dependency injection, testing, getting what you want into the template, etc. And Angular isn't what you'd call a micro framework (see Django vs Flask or Bottle from Python world, for example). So of course Angular is large; it tries to solve alot of problems for you (how well it does so is another story). Anyways, the take-away (from my point of view) is that much of the work that used to be done by server-side guys can now be done by front-end guys. So they have to learn all the same concepts and struggle with all the same problems to be effective.
Ronsenshi 12y ago
90% is certainly high. But he's not that far from the truth. A lot of companies do expect anyone working with JS to know Angular... which is not good for me. I'm really not a fan of that framework.