Live data from Hacker News

Is Angular 2.0 ready?

splintercode.github.io

41–48 of 48 posts

Re: Is Angular 2.0 ready?

#41
post #30

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.

The architecture problem was solved separately in Flux: https://facebook.github.io/flux/docs/overview.html

Re: Is Angular 2.0 ready?

#42
post #7

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

In theory it will be. In practice, not yet because the documentation has a lot of gaps and error messages aren't that good yet. Still, I'm liking it. (I'm trying out the Dart version.)

Re: Is Angular 2.0 ready?

#43
post #39

Earlier quoted context omitted.

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…

> A lot of people still seem to really like Meteor. Meteor officially supports React and Angular. Meteor is a web and mobile development platform, not a front-end framework.

True, but by default it doesn't use React or Angular and provides Blaze for creating UIs.

It supports React and Angular as of recently, I suspect, simply to maintain itself as a competitor to other stacks, due to the extreme popularity of React and Angular.

Re: Is Angular 2.0 ready?

#44
post #32

Angular 1.x to 2 reminds me of the transition that Flash made from ActionScript2 to ActionScript3. AS2 had a bunch of newfangled conventions just like Angular and then AS3 came along and made everything more sensible. Speaking of front end frameworks though. I wonder what happened with Enyo and why that didn't take off.

Enyo was/is an amazing web component framework, but I think the whole HP webOS debacle pretty much scared people away from adopting it, due to uncertainties about it's future ownership and development. I believe it's still in use in the LG webOS TV SDK, at least.

Re: Is Angular 2.0 ready?

#45
post #30

Earlier quoted context omitted.

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.

The architecture problem was solved separately in Flux: https://facebook.github.io/flux/docs/overview.html

...and Flux is a philosophy or recommendation, not an implementaton. There are various independent Flux implementations out there, but none that have been battle-tested at the enterprise level AFAIK. Plus, from recent rumblings, Facebook seems to be moving "beyond Flux".

Re: Is Angular 2.0 ready?

#46
post #30

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.

With Reflux or similar, you have everything you need. Simple to build UI, simple to hookup to backend, simple to dynamically update backend and front end based on change or events on data.

When you say it's not a "framework" I don't even understand what you mean by "framework". If you mean a system that locks you into one way of doing things and is hard to integrate with other tools, then by all means, it's not a framework, and then I don't want it anyway.

Re: Is Angular 2.0 ready?

#47

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.

How many job descriptions do you see looking for "experience in JavaScript with at least one current framework"?

Compare that to the number of job ads looking for "experience with Angular".

I agree that it shouldn't be that way, but the hiring process is badly broken in most places.

Re: Is Angular 2.0 ready?

#48
post #30

Earlier quoted context omitted.

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.

With Reflux or similar, you have everything you need. Simple to build UI, simple to hookup to backend, simple to dynamically update backend and front end based on change or events on data. When you say it's not a "framework" I don't even understand what you mean by "framework". If you mean a system that locks you into one way of doing things and is hard to integrate with other tools, then by all means, it's not a fra…

> When you say it's not a "framework"

I never said that , don't put words in my mouth. The rest of your comment is irrelevant since you're making stuff up.

Post reply on HN