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

81–90 of 139 posts

Re: Angular 2 Release Candidate

#81

Post by wiradikusuma »

mattetti wrote: post #53
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…

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

Re: Angular 2 Release Candidate

#82

Post by reitoei »

robwormald wrote: post #72
craigvn wrote: post #22

Earlier quoted context omitted.

It is the million dollar question. If you are building a large product with an expected life of 10+ years, can you trust Angular to still be maintained?

Angular 1.x has been around since 2009 - 7 years - that predates pretty much every framework in use today, before modules (commonJS, let alone ES6) were widely in use, etc. At some point, we had to make a decision to be forward looking towards the future of the language. Support for 1.x won't disappear for some time. Angular 1.5 had a number of big upgrades - a focus will be easing the transition to 2.x over time ( .…

You're about 3 years out I'm afraid: https://github.com/angular/angular.js/releases/tag/v1.0.0

Even the earliest pre 1.0 releases of Angular weren't until late 2010.

Re: Angular 2 Release Candidate

#83

Post by glass-animal »

viraptor wrote: post #30
robwormald wrote: post #10

Lots more work to do here, but we're pretty happy with how the core looks! For those worried about size (which has absolutely been a fair concern over the alpha/beta process) - here's a "hello world" built with Rollup and our offline template precompilation. Clocks in at 200kb min/47k gzipped, with a bit more room from optimization over the next couple of weeks... https://ng2-compiler-test2.firebaseapp.com/

That seems a lot for: Hello world hello child (yes, I know it's not the same under the covers - take it as a comment on the ecosystem, not on the implementation (although it can be a comment on dead code detection too))

200k un-minified is huge!

Re: Angular 2 Release Candidate

#84

Post by romankolpak »

samuell wrote: post #8

When I read up about Angular 2 a year ago or so, based on my very shallow understanding it seemed like the perfect combination of the automagics of Angular 1, and the light-weightedness of React. But what do you JS folks think about this?

What gave you the impression of light-weightedness though? My understanding was that Angular 2 is aiming at being a fully featured (and thus heavy) framework.

Re: Angular 2 Release Candidate

#85

Post by glass-animal »

robwormald wrote: post #9

Angular core team member here, happy to answer questions

One thing that interests me about Angular 2 a bit more than React is the web components support.

With web components finally going native (surprisingly, led by Safari!), will Angular 2 see any big speedups, and will the size of the hello world app come down (200k is kind of huge)?

Also, I've seen a few tutorials on using Angular 2 with Polymer, but it seems complex. Is Google working on making these work together better? Will I be able to create Angular 2 web components and use them with Polymer web components?

Re: Angular 2 Release Candidate

#87

Post by paganel »

SeriousM wrote: post #51
merb wrote: post #47

After taking a look at Angular2 I definitv know that my when I need to rewrite my app with something like that: app.AppComponent = ng.core.Component({ }) .Class({ }); from angular.component('name', {}); I will go a totally other route than upgrading. I mean wtf. the JavaScript Part of Angular 2 is horrible. Since I'm on a Scala Server I possible try to look at Scala JS and rewrite something. It's too bad that our "ap…

No problem. People like you have to stick with the old stuff because of this mindset. I mean WTF is bugging you? It's just code you have to write in order to get the thing running. You could also complain about the empty object in the angular1 method.

> I mean WTF is bugging you?

Not the OP, but having to write four lines of code instead of one does not look that good. Less is more. Code bloat should be called out.

Re: Angular 2 Release Candidate

#88

Post by spdy »

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

React is much more of a JS approach - sure the core library is smaller but in the end you throw in a bunch of libraries to compose your own framework

Thats the reason i decided against React. After so many years of programming i really like opinionated its so time consuming to figure out which major library component (*flux) will be maintained down the road and have enough momentum behind it.

And the combination of Angular2 with Typescript it really nice

Re: Angular 2 Release Candidate

#89

Post by MrDosu »

I just love how the same people that called me the devil for using WPF back when .NET 3 came out are now calling me about angular with 'have you heard about this new and exciting paradigm?'...
Post reply on HN