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

131–139 of 139 posts

Re: Angular 2 Release Candidate

#131

Post by notsotrue »

spriggan3 wrote: post #118
notsotrue wrote: post #107

I'm looking forward to trying this out. Having written Ember, Angular, and React apps now, I feel like they are all getting closer, but a lot of rough edges still exist. Ember: interesting framework, but all too often, you would hear a team mate say "wait, why is that working, it shouldn't be?" Mixed with equal parts "logically, that SHOULD work, what am I missing?" React: I love the component focus, and redux is pre…

> However, the more complex an app, the less Angular 1 serves. That's not really true. The problem is that all three frameworks are supposed* to require the same discipline when it comes to managing state, but only React forces that discipline onto the developer. I'm not saying React is better, but learning from React is important to be able to write maintainable applications in any framework. You don't want to have…

I'm curious, what would you consider a complex app?

Re: Angular 2 Release Candidate

#132

Post by zoechi »

robwormald wrote: post #13
symlinkk wrote: post #12

Earlier quoted context omitted.

Why is everything packaged separately now? Also, any ETA on 1.0?

couple of reasons. one big one is flexibility. angular2 (er, @angular) runs on client, server, native (react native/nativescript) and we hope many other platforms in the future. this lets us packages for common dependencies for various platforms, as well as enabling us to not ship the template compiler for precompiled apps. the other is providing a single entry point to each of those packages, which makes it easy to…

Great work! Like it a lot - especially with Dart ;-)

Re: Angular 2 Release Candidate

#133

Post by ejsmith »

Aurelia (http://aurelia.io) is the ONLY framework that I have seen where you DON'T see the framework when you look through the code. You see YOUR app and YOUR logic. To me this is incredibly important for the longevity and simplicity of your code base. Please people, do yourselves a favor and checkout Aurelia.

Re: Angular 2 Release Candidate

#135

Post by jffry »

glass-animal wrote: post #83
viraptor wrote: post #30

Earlier quoted context omitted.

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!

FYI they said at today's ng-conf sessions that with the recent release candidate, they have cut that from 200K to 40K and that there's still more room to shrink.

Re: Angular 2 Release Candidate

#136

Post by jffry »

glass-animal wrote: post #85
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 bet…

I can't answer your other questions competently, but at ng-conf today, in the keynote [1], they announced improvements that drop Angular2 down smaller than 1.x, and that they have plans to continue

[1] 9:02 mark in https://www.youtube.com/watch?v=gdlpE9vPQFs&t=9m2s

Re: Angular 2 Release Candidate

#137

Post by zkhalique »

zxv wrote: post #39
zkhalique wrote: post #17

Earlier quoted context omitted.

React is just about dirty-checking the view, while Angular dirty-checks the model. I mean, seriously, that's the main difference conceptually. You just modify some data structure and both frameworks will update some view.

I was surprised to find that Angular has a limited duration time window during which changes will update the view. In my case, symptoms were observed only after deployment, for user who had a high latency connection between their browser and the server. One could mitigate this by calling $scope.$apply() after every change. But if you have to apply() all changes, then what's the point of having angular handle synchron…

In our platform, we just let the developer call a function manually after updating the state of a tool. So it is event-driven reactive changes.

Yes, shockingly, we don't save those keystrokes, but we also don't have the elaborate dirty checking. The developer of a component is extremely likely to make sure during development that the update to a state has updated the view. Of course, you could just hook up React or VDOM or mirthril and it's totally complementary to what we do.

Re: Angular 2 Release Candidate

#138

Post by CCPony »

mercurial wrote: post #114
rubber_duck wrote: post #74

Earlier quoted context omitted.

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

Note that Typescript with React is totally possible.

Well, yes... and no. When I tried to use Typescript with React I couldn't help but feel like I was squeezing a square peg through a round hole. Eventually you can do it, but it's an effort. Ultimately you end up with something marginally better than plain JS.

Since virtually ALL available React tutorials, courses, quick starts, etc are written in JS, there is very little support out there for TS.

With Angular2, it's all TS all of the time. And, to me, that's incredibly important.

Re: Angular 2 Release Candidate

#139

Post by dbbk »

oolongCat wrote: post #58

Ask HN: Why would I spend time upgrading my Angular1 code to Angular2 when I can migrate to React Or Vue.js. I am honestly intrigued as to what Angular2 offers, that other JS frameworks wont?

You wouldn't? That would be a waste of your time. Angular 1 isn't going to suddenly stop existing.
Post reply on HN