Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2 Core

docs.google.com

Post reply on HN
Print view View original

51–60 of 279 posts

Re: Angular 2 Core

#51

Post by gloverkcn »

colinramsay wrote: post #38
emilis_info wrote: post #28

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 c…

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?

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.

Re: Angular 2 Core

#52

Post by dodyg »

This is what is shit with JavaScript frameworks, no respect to backward compatibility. Imagine if these kind of API churning happens in C++ or other languages.

Re: Angular 2 Core

#53

Post by pavlov »

colinramsay wrote: post #38
emilis_info wrote: post #28

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 c…

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?

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.

Re: Angular 2 Core

#54

Post by skore »

robert_tweed wrote: post #43
mateuszf wrote: post #39

Earlier quoted context omitted.

React is just newer. Give it some time.

Indeed. If number of contributors is the only metric that counts then, since React has more contributors than jQuery, I guess that means we shouldn't bet on jQuery. Nobody's gonna be using that fly-by-night project in a year!

That's why I wrote "for reference". jQuery, of course, is a different kind of library.

A proper argument would be: jQuery has about three times the contributors that mootools has. If I had to decide between mootools and jQuery, I'd pick the second because of that metric alone, yes. (And this is how the market ended up playing out.)

Angular (born Jan 2010) has 2.5 times the number of contributors of ember (born Apr 2011), 5 times of React (born May 2013). I'm not just trying to find a reason to dismiss React and I do realize that it is still young. From a business standpoint, though, the choice couldn't possibly be any clearer.

I do agree that React has gathered a sizable crowd in a short time and it's definitely on my list of projects that I keep an eye on. But it's simply too young to warrant the same kind of investment that I have personally made into Angular.

Re: Angular 2 Core

#55

Post by kuni-toko-tachi »

realusername wrote: post #47

I'm quite disappointed by this presentation, I see only new syntax everywhere for approximately zero benefit. There is not even any mention to the Object.observe integration which would be the most exiting feature to improve Angular apps. Angular looks and feels now like a Java framework, with ugly decorators and bloated APIs, that's really sad...

Agree 100%. Things like dependency injectors have no real place in JavaScript, where programmatic wiring and modules already solve the problem in an idiomatic way. Angulars modules factories services etc are absurd and attempt to reinvent what the language naturally provides.

Re: Angular 2 Core

#56

Post by binocarlos »

dodyg wrote: post #52

This is what is shit with JavaScript frameworks, no respect to backward compatibility. Imagine if these kind of API churning happens in C++ or other languages.

I'm sat right now coding a bunch of new stuff in angular 1.2 - it was feeling sweet until I read this - now it feels old and outdated. Time to just ignore the massive race to reinvent the framework and just get some stuff done I think.

Re: Angular 2 Core

#57

Post by emilis_info »

colinramsay wrote: post #38
emilis_info wrote: post #28

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 c…

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?

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.

Re: Angular 2 Core

#58

Post by colinramsay »

Jgrubb wrote: post #50
colinramsay wrote: post #38

Earlier quoted context omitted.

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?

> 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.

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.

Re: Angular 2 Core

#59

Post by kuni-toko-tachi »

Jgrubb wrote: post #50
colinramsay wrote: post #38

Earlier quoted context omitted.

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?

> 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.

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?

Re: Angular 2 Core

#60

Post by colinramsay »

bryanlarsen wrote: post #25
gasping wrote: post #24

Earlier quoted context omitted.

> you'll never go back to anything else. React completely changed the way I thought about rich clients. It took me a little longer than 2 days, I went into React with an absolute hatred of anything Javascript and came out 2 weeks later loving it. There is something to be said for a library that can wash away over 10 years of built up anger for a particular technology. It's not just another revamped library thrown int…

You are absolutely right. Which is why I'm so excited about Angular2. It's the first post-React client-side framework to come along. (as opposed to React which is more of a library than a framework, although it definitely pushes the boundaries of that...)

Technically you're right - it is post-React. But in order for it to really have learned from React I think we'd have to wait a little while longer, because the industry is still learning what React and Flux can really bring to the table. For me, one of those things is simplicity, and that's something that I feel Angular sorely lacks.
Post reply on HN