Live data from Hacker News

Angular 2 Survey Results

angularjs.blogspot.com

61–70 of 82 posts

Re: Angular 2 Survey Results

#61
post #37

It's a shame that jQuery was included within "What frameworks other than Angular 1.x do you use regularly today? (choose multiple)". Why not throw lodash/underscore in too?

I can kind of see how jQuery + mainstream jQuery usage patterns would get grandfathered in as a sort of ad hoc, primordial framework.

Re: Angular 2 Survey Results

#62
post #54

Hey, UI Router lead dev here. I'm interested in any & all feedback people have regarding Component Router vs. UI Router, what they like/don't like, and whether or how much they'd like to see UI Router support for Angular 2.

Just wanna say, huge fan of UI Router, thank you so much for your hard work! Makes my life so much easier :)

Same boat here. Really like UI Router. $stateParams saves me so much time.

Re: Angular 2 Survey Results

#63

There were about a half dozen responses for Dart and 1 for Closure Compiler. In other words, at least 7 Googlers submitted survey responses. ouch.

Just because someone likes dart, doesn't mean they are from google. As an example I really enjoy dart, and I am not from google

Re: Angular 2 Survey Results

#64
post #63

There were about a half dozen responses for Dart and 1 for Closure Compiler. In other words, at least 7 Googlers submitted survey responses. ouch.

Just because someone likes dart, doesn't mean they are from google. As an example I really enjoy dart, and I am not from google

It's a joke

Re: Angular 2 Survey Results

#65

It's funny how so many development communities feel like they need to start over and create an entire new framework. Perl 6, PHP 6 (which was never released), the disaster that is Python 2/3 (many standard libraries were renamed breaking a ton of libraries, and now Angular. PHP, which is hated by many here because it isn't hip, at least allows you to run 4 code on the 5 interpreter with no issues. When Microsoft did…

haha, I guess I hurt the feelings the open source community. BOO HOO!!

You're not really adding anything to the conversation. If you even did a cursory search as to the motivations behind why Angular 2.0 was a rewrite you'd learn that it has everything to do with compatibility with web components and ES6 and nothing to do with "money" as you say (I'll save you the two seconds of effort: http://eisenbergeffect.bluespire.com/all-about-angular-2-0/). In fact, it was a huge blow to Angular when they announced they would be introducing such sweeping changes to the framework. Remember that the web is a constantly moving target and assumptions you make today may no longer be relevant two years from now.

Re: Angular 2 Survey Results

#66
post #14

Earlier quoted context omitted.

Did you see the blog post from last week on Angular's efforts to help developers transition from 1 to 2? http://angularjs.blogspot.com/2015/08/angular-1-and-angular-... As for little/no benefits, that is certainly not true. Angular 2 is going to be better in almost every way from Angular 1 and there are many great apps built off Angular 1. If you haven't tried Angular 2, I suggest giving it a go once the they get to…

At a first glance the link you provided promotes double insanity: angular 1 mixed with angular 2 (because angular 1 was not complex enough when angular 2 decided to simplify it with new syntax and requiring typescript which seems to require node.js). Is there some documentation for angular 2 with plain javascript (no typescript) for people who want to keep it simpler ? Can you provide some links ? Thank you.

if you consider a "node.js" requirement (read: a build step) too complex for your projects, you're probably correct in that you don't need any version of angular, react, ember, or anything else.

Re: Angular 2 Survey Results

#68

Hey, UI Router lead dev here. I'm interested in any & all feedback people have regarding Component Router vs. UI Router, what they like/don't like, and whether or how much they'd like to see UI Router support for Angular 2.

My vote is for the Angular team to stay away from ui-router because you are difficult to deal with, based on multiple discussion threads I've seen 'round the net. Your code is good but not sufficiently better than component router to justify the friction.

You're right. Sorry about that.

Either way, thanks for the compliment on the code. :-)

Re: Angular 2 Survey Results

#69
Unrelated to this specific survey, but as somebody unfamiliar with Angular, having both angular.io and angularjs.org with neither making the version difference clear at a glance is confusing as heck.

Re: Angular 2 Survey Results

#70

Hey, UI Router lead dev here. I'm interested in any & all feedback people have regarding Component Router vs. UI Router, what they like/don't like, and whether or how much they'd like to see UI Router support for Angular 2.

We started using ui-router recently and from quick profiling of rendering it looks like a lot of time is spent in ui-router transitions (chained promises) and in generating/validating ui-sref links. I don't know if this will get linearly worse with increasing size of application, but anyway this is why I'm interested in checking out Component Router.

Do you have any pointers to differences between Component Router and ui-router? I'm especially interested in pitfalls of both.

I haven't debugged ui-router much yet, but maybe I'm doing something wrong (which sometimes happens in Angular world, e.g. when people use $timeout(fn), when in given situation they should actually do $timeout(fn,0,false)...).

Post reply on HN