Live data from Hacker News

Does Angular 2 live up to the hype?

cycligent.com

31–40 of 44 posts

Re: Does Angular 2 live up to the hype?

#31
post #28
post #21

Earlier quoted context omitted.

To add to your point, I feel that React/Redux is easier to debug. Redux has the developer tools, which allow you to rewind state as well as hot module reloading, which means you can rewind state, and then replay it with your code changes. This means you don't need to log back in to your app, navigate to where you were previously at, and then recreate whatever extra state each time you try a fix. The functional approa…

You can use Redux with Angular 2, and it works quite well! The dev tools work the way you'd expect them to. Webpack hot module loading works well Angular 2 as well. I agree that JSX is easier to debug. The Augury[1] Chrome extension serves the same purpose for Angular 2 as the React Dev Tools extension does for React. That's not to say that React isn't great too! I like it lot. [1] https://augury.angular.io/

How does it do with synching your route state with the redux store? I remember when I played with it (think routing has been replaced twice since) that was the real beast, though redux was a pretty nice fit other than that.

Re: Does Angular 2 live up to the hype?

#32

I've only briefly tried Angular 2 so I accept I may be wrong about this, but it feels like there's too much friction required to add a new component which discourages me from doing so. It feels like you have to create too many files and add too many lines here and there to connect everything up each time. Having reusable components is great but trying to make everything reusable when it probably won't be reusable (i.…

Modules in RC5 mostly fixed that. You still define all the dependencies and directives, but they're all packaged into a module file, and then you can use use any components by dropping them into your template. Getting something like an Angular 2 snippet tool will also speed you up a bit.[1]

[1] https://atom.io/packages/angular-2-typescript-snippets

Re: Does Angular 2 live up to the hype?

#33
post #23

It sounds to me like it's a great framework, but "Angular 2" is a misnomer at this point. Maybe the "Angular" name will entice 1.x users to it, but it seems like the Angular team could have created "MasterBlaster 1.0, the successor to Angular" or something, still got some hype, and avoided a lot of grumpiness.

My vote was for "Angular Elizondo Mountain Dew Herbert Camacho" but the Angular team was already pretty committed to Angular 2 by then.

It's got electrolytes.

Re: Does Angular 2 live up to the hype?

#36
post #8

Earlier quoted context omitted.

Which additional tools would you recommend to combine with AngularJS if you are targetting a web app for both desktop and mobile?

Not GP but ionic is really solid. It helps to think of it mostly as a CSS framework with a tool chain for deployment and testing. Theres also a lot of examples and a pretty big community around angular + ionic.

Thanks. I haven't done webdev in many many years so all the new front-end & back-end frameworks are a bit overwhelming.

One thing I haven't decided yet is what to use to build the "pre-login pages". The SPA itself will be only accessible after a login page, but before login there will be a bunch of pages (Home/Blog/Help/etc..). Should I use Angular for those pages as well?

Re: Does Angular 2 live up to the hype?

#37

Personally, I think Vue.js is the way to go now. It is very simple and a highly thought out framework.

Just read through their intro. How is it any different than Angular? Instead of ng- they use v-?

Everything else. Vue is view layer only. Major difference would that Vue uses dependency tracking for change detection while angular 1 uses digest cycle & dirty checking.

For more differences, consider this (likely biased) comparison: http://vuejs.org/guide/comparison.html#Angular-1

Re: Does Angular 2 live up to the hype?

#38
post #13

A more useful question to answer would be should I use Angular or React?

Are you okay picking your state management paradigm, and additional tooling? Are you more functional or OO minded. Do you lean towards TypeScript/static typing? Do other people you are going to be working with have experience with either of the tools/platforms? For me, imho React + Redux + fetch api go a really long way to get you there, combined with material ui, or react-bootstrap with react-icons you're all but se…

If you want redux in angular 2, take a look at https://github.com/ngrx/store

Re: Does Angular 2 live up to the hype?

#39
post #34

Can anyone comment on the probability that Angular 2 will be subjected to the same fate as Angular 1 -- namely, abandonment? That really hurt and I am reluctant to trust these people with my time and effort again.

Close to 100% when approaching infinity.

Of course the more important question is how soon it will be abandoned. Considering Google is currently advocating Web Components with Polymer as the future of the web (google "PRPL" for the details) I think Angular 2 is technically dead on arrival.

However Google has a tendency never to settle on a single solution (see TypeScript vs Dart vs Go, Hangouts vs Allo vs Duo, Android vs ChromeOS and even Orkut vs Google+). So they will probably keep Angular around until they come up with something new.

That said, Google has a tendency to yank out support as they see fit in the name of progress (e.g. how Angular 1 dropped IE8 support on the spot). So I wouldn't expect any obvious warning signs in advance to Angular 2's eventual demise.

Re: Does Angular 2 live up to the hype?

#40
post #28

Earlier quoted context omitted.

You can use Redux with Angular 2, and it works quite well! The dev tools work the way you'd expect them to. Webpack hot module loading works well Angular 2 as well. I agree that JSX is easier to debug. The Augury[1] Chrome extension serves the same purpose for Angular 2 as the React Dev Tools extension does for React. That's not to say that React isn't great too! I like it lot. [1] https://augury.angular.io/

How does it do with synching your route state with the redux store? I remember when I played with it (think routing has been replaced twice since) that was the real beast, though redux was a pretty nice fit other than that.

That's a good question; I didn't try it.

On the bright side, if you don't mind diving one layer below the surface, the code for react-router-redux is short, well written, and easy to understand: https://github.com/reactjs/react-router-redux

Even if the equivalent already exists for the current iteration, you could probably write your own in an afternoon without rushing yourself too much.

Post reply on HN