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

Angular 2 Release Candidate

github.com

Post reply on HN
Print view View original

91–100 of 139 posts

Re: Angular 2 Release Candidate

#91

Post by blowski »

rubber_duck wrote: post #74
jalami wrote: post #5

I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…

React and Angular are two very different experiences. Using Angular 2 with TypeScript is almost like using WPF and C# on the desktop - it has that enterprise framework feeling - hierarchical DI everywhere, everything out of the box (DI, routing, events, forms, etc.), classes and OO are the foundation, decorators, even "functional" parts adopts RX from .NET. Using Dart gets you even more stuff working "out of the box"…

I have done some small personal projects with React, Angular 1 and 2 just for learning, and I agree with your assessment. If I were building a production system with a small team of intermediate non-specialists, I would use Angular every time. For a front end dev, it's like comparing SASS (React) to Bootstrap (Angular).

They're both good at what they do, but they have different sweetspots in terms of the problems they're good at solving.

Re: Angular 2 Release Candidate

#92

Post by admnor »

wiradikusuma wrote: post #81
mattetti wrote: post #53

Earlier quoted context omitted.

We've been slowly migrating https://splice.com from Angular 1 to Angular 2, so far it's been great. We switched to TypeScript, we cleaned up our code organization. We are writing new components in ng2 and migrating old code we we go. The betas have been somewhat painful with bugs and breaking changes, but that's the price to pay. When it comes to performance and consistency, ng2 is a big winner. Why not React you mig…

Re: switching to TypeScript, manual rewrite or transpilation? My codebase is CoffeeScript, so I'm also interested to hear if you have any experience with that (with Angular 2).

My advice would be to compile your CoffeeScript to JS, then start from there. That's assuming that CoffeeScript still produces readable, idiomatic JavaScript...?

As of TypeScript 1.8(?) you can set an "allowJs: true" flag in tsconfig.json, which tells TypeScript to include JS files in your build.

Then you can just manually add type annotations and ES2015/2016 goodness to your code and change the suffix to '.ts' on a file-by-file approach.

I'm doing this at the moment with a fairly large AngularJS 1.5 project, using Webpack with awesome-typescript-loader as the build system, and it's working perfectly so far.

Re: Angular 2 Release Candidate

#93

Post by admnor »

ihsw wrote: post #7
jalami wrote: post #5

I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…

As someone that works for a #1 company, I am living that anxiety. We all know it will be inevitable, and we all know it will be hell rewriting it. If it's more than copy-pasta then I doubt it will be received well. And #2 is spot on -- React is eating Angular's lunch. I'd love to use it at work but I can't, and I don't think I'm the only one.

React is not "eating Angular's lunch". The only reason it seems that way is that it is impossible to have a conversation about Angular on the internet without a horde of React zealots turning up and banging on about it.

Recommending React to somebody who's considering Angular is like recommending tyres to somebody who's shopping for a car.

Re: Angular 2 Release Candidate

#94

Post by iSnow »

jalami wrote: post #5

I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…

I knew it before opening the threat. What would the highest ranking post be, someone discussing the merits of Angular 2 or someone doing the usual "yeah nice, BUT REACT!"?

There are lots and lots of shops that - for one reason or another - don't care about React. And frankly for someone who works with Angular 1.x, React might just not be that interesting.

Re: Angular 2 Release Candidate

#95

Post by iSnow »

maxharris wrote: post #2

I'm coming at this from the perspective of someone who has never used Angular 1.x or 2.x. I guess the first thing on my mind is: can I make Angular 2 work just like React does? Is there any way to use it without making/(being allowed to make) separate HTML templates and CSS files? If not, this is a serious disadvantage. Having the view layer scattered across 3X the files (vs React) would make it very hard to follow t…

If you want React, just use React.

Re: Angular 2 Release Candidate

#96

Post by k__ »

admnor wrote: post #93
ihsw wrote: post #7

Earlier quoted context omitted.

As someone that works for a #1 company, I am living that anxiety. We all know it will be inevitable, and we all know it will be hell rewriting it. If it's more than copy-pasta then I doubt it will be received well. And #2 is spot on -- React is eating Angular's lunch. I'd love to use it at work but I can't, and I don't think I'm the only one.

React is not "eating Angular's lunch". The only reason it seems that way is that it is impossible to have a conversation about Angular on the internet without a horde of React zealots turning up and banging on about it. Recommending React to somebody who's considering Angular is like recommending tyres to somebody who's shopping for a car.

I have the feeling they're both just for a different crowd.

Re: Angular 2 Release Candidate

#97

Post by executesorder66 »

rk06 wrote: post #37
ihsw wrote: post #7

Earlier quoted context omitted.

As someone that works for a #1 company, I am living that anxiety. We all know it will be inevitable, and we all know it will be hell rewriting it. If it's more than copy-pasta then I doubt it will be received well. And #2 is spot on -- React is eating Angular's lunch. I'd love to use it at work but I can't, and I don't think I'm the only one.

React is not the only competitor either. Aurelia and Vue are there to make up for react's problems.

Mithril is also a pretty good competitor.

http://mithril.js.org/

Re: Angular 2 Release Candidate

#98

Post by [deleted] »

jalami wrote: post #5

I realize a lot of companies flocked to Angular and it's used in a lot of places, but from the outside it seems to be fighting on two fronts. 1. Companies currently implementing it not wanting it to change or for there to be a quick and painless migration from 1.x to 2.x. So, less change, more hand-holding. The web changed a lot though, so its change is understandable. 2. Trendsetters and upcoming companies looking f…

[deleted]

Re: Angular 2 Release Candidate

#99

Post by crucialfelix »

jbergens wrote: post #76
crucialfelix wrote: post #63

Earlier quoted context omitted.

I've used flux and redux in angular for years. You can write purely functional directives. Angular is much more than just a view library. I've built quite a bit in both react and angular.

That's nice but then you don't have the "angular is the standard and I don't have to choose anything" advantage anymore.

But my code is more flexible, less dependent on the framework it's deployed in. So I can more easily survive things like "migrate to ng2"

Re: Angular 2 Release Candidate

#100

Post by qaq »

madeofpalk wrote: post #54
qaq wrote: post #49

Earlier quoted context omitted.

CSS animations do not work when you need to morph distinct components in complex coordinated manner. They are significantly slower then velocity js. Doing things available with quality solutions such as Ember liquid-fire are simply not possible.

Animations work really well with React! The Animated library (originally from React Native) gives you some pretty basic but powerful primitives to build whatever animation you need.

On route transition you want to animate morphing unrelated components between before transition components and after transition components. You will not be able to do this in functional manner. You will not be able to do this with CSS animations. Example of how this is done with Ember liquid fire. https://www.youtube.com/watch?v=vq_BcIFM8Rc
Post reply on HN