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

Is Angular 2.0 ready?

splintercode.github.io

Post reply on HN
Print view View original

21–30 of 48 posts

Re: Is Angular 2.0 ready?

#21

Post by kylecordes »

bluejekyll wrote: post #16

After working with react, IMO angular 2 is probably going to come to the game too late. If it's anywhere as complex as 1, then I see no point in using it. React takes the cake in simplicity and expressiveness. It's also a truly component oriented system.

From looking at the Angular 2 alpha, design documents, etc., it looks to end up with considerably less accidental complexity (from an application developer point of view) than version 1, and it has a lot of ideas under the hood which are reminiscent of React.

I think the most visible difference will remain that React is code centric, with templates as a sort of special case of code. Angular (1, 2) is more explicitly divided between code and template.

I believe the main driver in choosing between them will not be technical, but cultural. There are many organizations where considerable value is ascribed to the notion of code versus template, such organizations might lean toward Angular (especially in version 2) over React and friends.

Re: Is Angular 2.0 ready?

#23

Post by hodwik »

lolive wrote: post #7

Off topic question from a newbie: is Angular 2.0 simpler to learn (than Angular 1.x)?

It looks that way in the long run, although there will be a period where tutorials for Angular 1 will be superior to those for Angular 2.

Re: Is Angular 2.0 ready?

#24

Post by kevindeasis »

lolive wrote: post #7

Off topic question from a newbie: is Angular 2.0 simpler to learn (than Angular 1.x)?

Angular 2 looks way easier to understand. That is from the perspective of someone just starting out. Although note alot of things changes in Angular 2. So some tutorials may be out of date.

Re: Is Angular 2.0 ready?

#25

Post by grayrest »

JustSomeNobody wrote: post #9
bryanrasmussen wrote: post #2

Is angular 2.0 still not going to be backward compatible? Why do I see all these jobs requiring angular if it isn't!?!

Why are you looking for jobs that specifically require Angular? You'd be better off in the long run looking for jobs that require Javascript knowledge and are familiar with at least one current framework. Those are the types of companies who will be more likely to upgrade their stack as technology progresses.

I doubt he's specifically looking for Angular jobs or likely any job at all. It's likely he's getting contacted by recruiters or just seeing job ads. The current trend is react but I run across node+angular postings regularly.

Re: Is Angular 2.0 ready?

#26

Post by _hadrian »

mrharrison wrote: post #20
bluejekyll wrote: post #16

After working with react, IMO angular 2 is probably going to come to the game too late. If it's anywhere as complex as 1, then I see no point in using it. React takes the cake in simplicity and expressiveness. It's also a truly component oriented system.

Not true, I still get recruiting emails every week asking for angular experience, which means there is probably a huge group of people locked into the angular framework, and since 2.0 will be backwards compatible, I'm sure a decent amount of people will be switching their angular 1.0 apps to 2.0. It will be easier then converting a whole angular stack to React and figuring out all of the other React libraries and fra…

Angular 2.0 is backwards compatible the same way that React is compatible with Angular 1.0... basically it's mainly just the new Router that makes it possible to use other libraries easier with 1.0.

Re: Is Angular 2.0 ready?

#27

Post by joshburgess »

bluejekyll wrote: post #16

After working with react, IMO angular 2 is probably going to come to the game too late. If it's anywhere as complex as 1, then I see no point in using it. React takes the cake in simplicity and expressiveness. It's also a truly component oriented system.

Honestly, there are plenty of other options out there besides Angular and even React, despite the tremendous hype around it at the moment.

Aurelia seems to be the best ideas from Angular + the best ideas from the creator's previous framework, Durandal, in one framework with much cleaner syntax and much less complexity than both Angular & Angular 2.0.

Ember has made some big updates recently, rewriting their rendering engine to use a virtual DOM.

A lot of people still seem to really like Meteor.

Mercury, Mithril, Ractive, JSBlocks, etc. are all smaller, lesser known projects with a lot of potential.

Re: Is Angular 2.0 ready?

#28

Post by aikah »

lolive wrote: post #7

Off topic question from a newbie: is Angular 2.0 simpler to learn (than Angular 1.x)?

There are more resources about Angular 1.x obviously.

What might be confusing is the whole AtScript/Typescript/Javascript thing.

I never found Angular 1.x difficult, but it's a bit like Rails, people might have the impression that they can learn the framework without learning the language at first place. Ultimately 1.x was limited by ES5 itself. That's what it was a bit confusing sometimes, especially with all the scopes and contexts stuff.

Re: Is Angular 2.0 ready?

#29

Post by JDDunn9 »

bluejekyll wrote: post #16

After working with react, IMO angular 2 is probably going to come to the game too late. If it's anywhere as complex as 1, then I see no point in using it. React takes the cake in simplicity and expressiveness. It's also a truly component oriented system.

React is not a framework...

Yes, the future will be web components, which would mean Polymer / x-tag until the spec is in all modern browsers. React will die when web components don't need polyfills.

Re: Is Angular 2.0 ready?

#30

Post by aikah »

bluejekyll wrote: post #16

After working with react, IMO angular 2 is probably going to come to the game too late. If it's anywhere as complex as 1, then I see no point in using it. React takes the cake in simplicity and expressiveness. It's also a truly component oriented system.

React never solved the architecture issue. With Angular 1.x and dependency injection , it solved that problem for you. React is just a view layer.
Post reply on HN