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

Angular 2 Final Released

angular.io

Post reply on HN
Print view View original

221–230 of 452 posts

Re: Angular 2 Final Released

#221

Post by eranation »

Kiro wrote: post #170
EugeneOZ wrote: post #39

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

> 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read. This is encouraging. I always thought that looked aweful so it's nice to hear that it actually makes sense.

Well it's a bit confusing / weird at first until you get used to it but the real confusing syntax is the mix of both for bidirectional binding, e.g. [(ngModel)], but after reading the docs it kinds of makes sense. Awesome job, love it so far.

Re: Angular 2 Final Released

#222

Post by NikhilVerma »

Nemcue wrote: post #195
NhanH wrote: post #77

Earlier quoted context omitted.

Any chance you can do a quick cons review too? Specifically comparing to the weakness of Angular 1 like bloated complexities, issue with custom directives or scope life-cycle.

Cons: 1. Typescript. If your team isn't familiar with it it's not trivial to get everyone on board. The up-front cost can absolutely be worth it in the long run, but there's some friction in the day-to-day work with managing type definition files and looking up esoteric lint-errors from the Typescript compiler. 2. RXJS. Canonical NG2 should use Observables, and rxjs is not a trivial library to learn the ins and outs…

It's very strange to me, any one of the cons from 3-6 will make me avoid a framework. Do you think the pros of the framework outweigh these serious cons?

Re: Angular 2 Final Released

#223

Post by Bahamut »

ergo14 wrote: post #153
prohor wrote: post #138

Earlier quoted context omitted.

Polymer and Angular 2.0 seems to have a lot concepts in common and I don't fully understand why they are going to compete, given they come from the same source. But for me it seems that Polymer nowhere picked up as Angular. When it comes to performance it is great in Chrome. In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-green browsers.

Have you actually benchmarked polymer in a non-chrome browser? It is much faster than Angular - somewhere around React performance. Polymer is picked up by big companies already whereas "no one"(big) is using angular 2.x for now. People here seem to project a weird bubble around Angular/React. > In other browsers not so. I hope v2 will be much better once they can get rid of the compatibility layer for other ever-gre…

A lot of big companies have been using Angular 2 for a while from what I understand. Canon was using it while it was in the alpha stages. Tesla went all in on Angular 2. Thomson Reuters had the largest Angular 1 app in the world, and they are moving to Angular 2.

The Angular team has made significant efforts to court them/cater to them, even employing a CSM, and two developer advocates. Those are just examples I've heard/interacted with in the wild, but I'm just a developer at a small company & not part of the Angular team.

Re: Angular 2 Final Released

#224

Post by pacoverdi »

gkoberger wrote: post #6

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

I lost so much time with Angular 1. I don't care how much v2 is better than v1, I'm not touching it with a ten foot pole (disclaimer: switched to React, not looking back).

Re: Angular 2 Final Released

#226

Post by boubiyeah »

k__ wrote: post #184
boubiyeah wrote: post #172

Earlier quoted context omitted.

That compiler flag is wonderful, and so is the newer 'strictNullChecks' I use these typings: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast... Then create my components like this: interface Props { } interface State { } class MyComponent extends React.Component { } and everything is typed correctly (beside setState which is impossible to type exactly as of today)

Maybe it was the type definition I used...

Stateless component:

  interface Props {
    bla: string
    ble: number
  }

  export default function MyComponent({ bla, ble }: Props) {

  }

Re: Angular 2 Final Released

#227

Post by danmaz74 »

subsection1h wrote: post #151
danmaz74 wrote: post #136

Earlier quoted context omitted.

Regarding the "Flux" frameworks, that's not a problem anymore - basically Redux (which improves on some of Flux's faults) has won. Its developer was hired by Facebook, so I guess it's kind of officially sanctioned now.

Has everyone who switched from Redux to MobX been informed that Redux won and they should switch back?

I'll admit that I hadn't heard so much about MobX yet. Will re-evaluate when I have time.

Re: Angular 2 Final Released

#230

Post by JustSomeNobody »

jasonkester wrote: post #133
lacker wrote: post #129

Earlier quoted context omitted.

And it needs tools upon tools upon tools to set up, whateverify, transpile and pack the files you write into something that can display in a browser. I think this was true six months ago but now there is create-react-app. You might want to try it out - you won't need to whateverify your code, you just need that one tool. Also it works on Windows. https://github.com/facebookincubator/create-react-app I want to edit so…

npm install -g create-react-app The fun thing watching the new world of Javascript is that overtooling is so built in to everything that nobody even realizes how many tools they're using. You can't even install this thing until you have the standard pile of javascript tooling in place. And it never occurred to them to even mention how to get said pile set up. Once set up, this still uses all the same stuff. It just r…

Exactly. It's "Oh, you don't like all the tooling, let's hide it all so when something breaks you have no idea where to look! HA! Isn't this FUN!"

No thanks.

Post reply on HN