r/angularjs • • May 05 '16

Angular 2 was never ready for a release candidate. RC0 was simply out because of ngConf, it is unstable and state of the router is a fucking mess

82 Upvotes

72 comments sorted by

4

u/fatty1380 May 06 '16

I haven't had the time to dig in, but every time I look at the router I'm shocked how incomplete and lacking it is. I'm coming from UI-router (as I expect most of us are) and I'm holding out for their ng-2 router before even considering a move.

Note: I've been really swamped and have not kept totally up to date on all this, so forgive me if my comments are out of date

23

u/m3wm3wm3wm May 06 '16

They completely ditched the router they had in beta, and introduced a shiny new router in RC, which is like alpha quality, undocumented, and untested. Basically, they made something up the night before the conference.

At the moment, if you want to start a new project with RC, you cannot really use a router.

Something is awfully wrong with software engineering these days. In the old days, release candidate meant getting close to stability, not back to alpha.

13

u/christophla May 06 '16 edited May 06 '16

You are entirely right about the state of things. Look at angular-material 1. Rc1 was never about stability. They made major architectural breaking changes through all the RCs. Im starting to think that the age-old development methodologies are completely lost on the new generations and their freewheeling approach to open-source. And i'm 37 - not some grandpa.

I have large teams of developers. The young ones are bright and fast as hell. But they have little concept of consequence. I constantly need to rope them in and guide their commits towards a greater end game.

To see Google suffer the same consequence really puts some serious doubts into my mind.

1

u/Gh0st1y May 06 '16

I'm a bit more than half your age, and idk if it's what I've read since I was a kid (hint SE books), but I couldn't agree more.

1

u/tbenbrahim May 06 '16

rc does not mean the same thing to the Angular team as what I think it means. I think it means that the release is feature complete, and that only bug fixes are contemplated before final release. No so. For example, I have an app with 50+ templates that is stuck on 1.5.0 rc0 due to lack of time to fix all the breaking changes between 1.5.rc0 and 1.5.0 final. For example, this: https://github.com/angular/angular.js/issues/13664. We ran across another one, but I do not remember what it was. In any case, I would not recommend anyone use Any RC version of angular for development, even if your release is weeks away, unless you have the time to change a bunch of code and retest everything you thought was DONE.

0

u/[deleted] May 06 '16

[deleted]

7

u/christophla May 06 '16

I think that my biggest concern is that a company like Google is allowing this crap to get through the filter. How can a 100 billion company not have direction, guidance, and architecture?

I somethings wonder if its just a bunch of people randomly doing shit in a campus. Without a professor in sight.

2

u/dvidsilva May 06 '16

Is a huge company but the angular manager is still a person and who knows what is he accountable for.he probably can make whatever decision and no one else at Google cares.

1

u/christophla May 06 '16

Semantic versioning is a blessing.

1

u/NerdyMcNerderson May 06 '16

Which angular does not follow.

2

u/moljac024 May 06 '16

Generally, in JS-land, you will not find much adherence to semantic versioning. Never mind that the most popular package manager, npm, is built around the idea.

8

u/fatty1380 May 06 '16

That actually feels somehow better to me. I agree with what sounds like a mislabeled "release candidate" but I'm glad to hear they scrapped the "new-router" - that project seemed to have nothing going for it and I look forward to checking out the "new-new-router". It's a shame they got our hopes up with the RC label, but I'm glad to hear they didn't try to keep going on what imho was a dead end from the start

10

u/ctanga May 06 '16

The ui-router team is bummed that we got no visibility at ng-conf this year.

ui-router ng2 support landed in 1.0.0-alpha.3.

Try the ui-router-ng2 quick start.

If you're upgrading your ng1 app, we have an ng1 to ng2 adapter which enables hybrid ng1/ng2 apps. Check out this branch of the 1.0 sample app to see the hybrid adapter in action.

I gave a (rather long) local meetup talk on migrating ui-router apps from ng1 to ng2; you can follow along with the slide deck

1

u/fatty1380 May 06 '16

That's awesome! I've been so swamped lately that, like I said earlier, I'm a little out of date on all of this.

Thanks for giving some solid links - I'll forward these along to my devs and try to take a look this weekend :D

1

u/angularfox May 07 '16

I was super bummed that I didn't see much about ui-router at ng-conf. That's what I was looking forward to seeing the most. I'm not convinced by the component router. Thanks for the links!

3

u/neb636 May 06 '16

I look at the router I'm shocked how incomplete and lacking it is. I'm coming from UI-router (as I expect most of us are) and I

Too bad Rob Eisenberg left the team. I think they stripped all the work he did on the router after he left. The Aurelia router is awesome. Much better than this poo Angular 2 new-router/new-new-router.

16

u/[deleted] May 06 '16 edited May 06 '16

Here's what happened: after Rob left, Brian Ford took over. Brian was coming straight out of his internship at the time, complete junior dev with no experience whatsoever in writing something like a router with complex state management and a great api. Since then, he's turned the thing into a complete and utter complex mess, when the angular team realized what was happening, they tried to fix it until very recently when they decided that they had to throw the whole code to the trash. This was a big blow on Brian's ego and he decided to leave google and the Angular team (he didn't even go to ng-conf). There were also rumors that Brian had been slacking this whole time and took advantage of the total kafkaesque situation that is the Angular 2 development, a JS framework that has been in development since 2013 and is still not ready! We're talking about a team that wrote their own language (AtScript) and then their own template js compiler for offline compiling, for a JS framework, crazy...

Quite sad, I still don't get why they won't go with ui-router, Brian wrote a doc about why they didn't do so but it seems like nothing that could not have been fixed in ui-router. Politics and ego happened, I guess that sums up the whole Angular 2 fiasco. Another thing is that Brad Green, although a nice guy, is a terrible manager (probably because managers aren't supposed to be nice all the time), the guy is a total push over and he can't say no to the gazillion features Igor wants to keep adding, he should have reported to higher management about the issue but he won't. Watching this trainwreck is really painful. (I work on a google product where we're forced to use Angular). Sometime I just think that they are a bunch of kids who were given too much money to develop the best framework ever and they decided to throw every feature at it that came to their mind or was popular at the time with no vision whatsoever, kind of like the homer simpson car.

1

u/joshmanders May 10 '16

Wow, this is all very interesting and makes me happy I jumped ship and went to React.

-5

u/cactussss May 06 '16

Rob Eisenberg left angular team with a near-complete router. That was his main task while working with Angular team. If it was all that great it would not be thrown away

2

u/cmgriffing May 06 '16

I think, maybe, you underestimate the politics of the whole situation.

1

u/Renegade-One May 06 '16

I still use ng-route. UI-router is still intimidating to me :(

3

u/ctanga May 07 '16

Hi! Would you do me a favor?

I'm working on a new ui-router site which will include some tutorials. You are the target audience for the tutorials. Would you mind trying the tutorials and tell me if it's still super intimidating?

http://christopherthielen.github.io/tutorial/ng1/helloworld

(this is a work in progress)

0

u/[deleted] May 06 '16

[deleted]

1

u/fatty1380 May 06 '16

I chose it initially because it was part of the boilerplate I was working from. I quickly learned that it provided all the bells and whistles I would expect from a router I was using to create a production level application to run my business off of. ng-route by comparison seemed like it was enough to build a simple "TODO MVC" implementation, but not much more.

I always liked this article on the topic: http://www.funnyant.com/angularjs-ui-router/ , and this stack overflow question provides a nice breakdown as well: http://stackoverflow.com/questions/21023763/angularjs-difference-between-angular-route-and-angular-ui-router

1

u/tbenbrahim May 06 '16

I use it because I need sub-routes. For example for route foo.bar. foo is attached to a form with a tab set, and foo.bar is attached to a particular tab on that form. ng-router did not support that last time I looked at it.

21

u/machinehead115 May 06 '16

I am here at ng-conf and although I haven't had a chance to dig into it myself they've had a few examples in the talks where they were referring to the beta router in their code and had to make the changes live to make it work. They also mentioned quite a bit that they just made changes to the code about 10 minutes before the demo, even today.

2

u/dvidsilva May 06 '16

Hey. I'm here too :) hope you're having fun

6

u/ctanga May 06 '16

I spoke candidly with two of the angular core team members yesterday.

I asked specifically if they felt the RC label was legit, or was added "because ng-conf". They both agreed that for ng2 core (component model, compiler, DI) the RC label is legit, but did not say the same thing about the router.

5

u/[deleted] May 06 '16

1

u/schippie May 06 '16

Seeing how happy i am with ngrx/store i am definitely going to give this a shot seems really promising

1

u/Lube May 07 '16

It rocks, I was worried no one here mentioned ngrx router.

7

u/[deleted] May 06 '16 edited Feb 20 '24

many obscene placid crowd price jellyfish full rinse thought disgusting

This post was mass deleted and anonymized with Redact

1

u/no_spoon May 12 '16

Can you elaborate on one example where angular 1 is a joke in comparison?

4

u/[deleted] May 12 '16 edited Feb 20 '24

square tidy hat gaze selective steer zesty enjoy vase relieved

This post was mass deleted and anonymized with Redact

1

u/no_spoon May 12 '16

Oh, thanks for clarifying.

5

u/telaelit May 06 '16

Amen to this!!! the docs for it aren't even completed yet. And the example that was mentioned in the change log didn't help at all

4

u/mhartington May 06 '16

I really think this is a bit much. I've been using ng2 for about a year now (back when things would change multiple times a day) and it's gotten whole lot better since then.

Is it perfect? No, no software is. Is the router done? No, probably not in honest. But thats fine, you can use something UI-Router if it matters that much to you.

Why don't we instead focus on seeing what we can do to help out and make NG2 better. Whether that's adding documentation or opening issues, or even submitting code.

2

u/wickedmike May 06 '16

You're right, but I think you're missing the point. Once again, marketing and PR are more important than the actual product. And we're developers, for god's sake, we're dealing with an exact science here. Everything we do is measurable, quantifiable and transparent (to your team or to the community if you're doing open source). You just can't wrap shit in gold foil and get away with it.

I thought the point of this NG-conf is to show off a complete product, but it seems like NG-conf was going to happen with or without the product. There is a lack of substance underneath the presentation layer.

10

u/mhartington May 06 '16

Once again, marketing and PR are more important than the actual product

I really don't think that's the case. Again, having used Angular 2 for quite some time now, I think this was a great time to actually show things off.

I thought the point of this NG-conf is to show off a complete product

No, the point of NGConf was to bring the community together, check out new tech and see what's being worked on/coming down the pipe line in Angular.

seems like NG-conf was going to happen with or without the product

Yeah, why would it not happen? Cancelling a community run conference because NG2 isn't "ready" really don't make sense.

And I don't want this to come across rude or anything, but give them a break. Saying there was a "lack of substance" is an insult to them. There's a lot of content at the conference, whether you think so or not.

2

u/[deleted] May 06 '16

Lets be honest. Google is not the only company to fall prey to the conference motivator. They are just the latest. I've worked at two companies where managers promised features for a conference which were never delivered. The developers knew the goals were wayyyyy out of line but either A. didn't voice it properly or B. were ignored by optimistic managers who were quite clueless to software dev timelines.

Apple, Microsoft and others pioneered this hype machine approach to conference releases, which they can pull off because they control everything. Open source is a whole different animal. People don't understand that in open source you start with x number of user stories but that as popularity goes up, the user stories spiral. This isn't a bad thing unless you're a damn fool and expect that you only have x user stories and plan hard timelines around it. See the golden triangle. Cost, quality, and time. You can optimize for only two...

2

u/[deleted] May 06 '16

B. were ignored by optimistic managers who were quite clueless to software dev timelines.

A. is usually because of B.

2

u/uberpwnzorz May 06 '16

I agree, they should have had another round of betas just for the router. IDK how they can completely change the router and call it a RC without a few rounds of fixes to it.

1

u/stormy11 May 06 '16

Should we consider React as the leading js framework at this time?

4

u/scottmmjackson May 06 '16

No. People have been too quick to dismiss the breadth of Facebook's license agreement. React isn't really open source, and it isn't an open standard either. Which is a shame, because JSX and react-native are really promising technologies from a pure functionality and tooling-based standpoint.

If we're exclusively talking about the frameworks that prioritize modular javascript, web components, and the other emerging standards, it's like talking about who the leading horse is before the race has started. I wouldn't count out any performant framework with a healthy community solely on the basis of whether or not it happens to be trendy at any one given time.

On the other hand, I think React's community is a ticking time bomb. The second someone with real money starts doing real business in the React ecosystem, you're going to see lawyers get involved in a really bad way. But people were warned about this, the same way they're warned about APRs on their credit card application- "It'll never happen to me, though..."

2

u/Amerzel May 07 '16

Can you expand on the react community comment. Why would lawyers be involved?

11

u/[deleted] May 06 '16 edited Oct 02 '16

[deleted]

4

u/Channel6 May 06 '16

Been using Aurelia the last 6 months or so and loving it...

3

u/rk06 May 06 '16

Angular 1.x is the leading js framework by a long shot.

then comes react ,vue and aurelia.

2

u/Gh0st1y May 06 '16

Is it worth it to go about learning ng2 at this point, if one doesn't have experience with either ng1.x or ng2?

2

u/rk06 May 06 '16

until ng2 is deemed production ready (and get few more patch releases), you should avoid it.

if you do not have experience with ng1 or ng2, then you should try learning ng1.

3

u/Gh0st1y May 06 '16

Oh, alright. Time to make like 60 tabs go away.

3

u/spritefire May 06 '16

It's in beta and has greater performance than Angular 1, so I wouldn't be so fast to close those tabs down. It does have a much steeper learning curve which has pushed a ton of devs away. Better performing + less devs = more money for you (if you want to pursue it as a career).

0

u/krisajenkins May 06 '16

Just learn Elm. JavaScript's going to keep breaking your heart.

5

u/Gh0st1y May 06 '16

But I like js.....

4

u/krisajenkins May 06 '16

I wish it liked you as much. I truly do. But it's been cheatin' on you for years with a null reference from the bad side of town. It's only gonna keep breakin' your heart, and I fear one day there won't be any more heart left to break.

Come on, let's leave this place, jump in a cadillac and drive out of this ng2-bit town. Waddaya say?

1

u/Gh0st1y May 06 '16

I love that, but mind explaining what you mean? I used to hate js, theb I read js the good parts and it changed that perspective for me. Its only been a bit, but I haven't had many problems so far..

0

u/[deleted] May 06 '16

[deleted]

2

u/krisajenkins May 06 '16 edited May 06 '16

"Elm isn't javascript" is precisely the point. And it definitely solves all the same business problems as Angular, without creating all the technical problems.

Seriously, it's a really good option. If the community isn't large enough for you, I encourage you to add to it by one. :-)

(Buuut...I'm not trying to troll anyone here. Someone just sent me to this thread and I couldn't resist adding another possible solution to the problem.)

1

u/eyko May 06 '16

Angular 1.x is the leading js framework by a long shot.

Let's at least limit that to > 1.5

1

u/benharold May 06 '16

No way. I'm still on 1.2 because IE8 still brings in cash.

1

u/eyko May 07 '16

What coins? Seriously? I feel for you bro

1

u/shadamedafas May 06 '16

Ember

1

u/rk06 May 07 '16

Sorry, forgot about ember

1

u/spritefire May 06 '16

I'd look at Polymer before moving to React. I heard a while back that the dev teams (angular / polymer) were working together which is probably where a lot of the energy has gone to. Also, React isn't a framework and there is a famous blog going around showing it has greater performance than angular 2, except the people who did the same blog/article forgot to include track by for angular 2 (and not for angular 1) which is why it shows angular 1 as a best performer between them all (including angular 2, even though this is definitely not the case).

2

u/ergo14 May 06 '16

Google is using polymer for their new beta youtube interface, youtube gaming and google play music interfaces. It seems to work quite nice for them.

1

u/iends May 06 '16

I remember seeing a similar article almost a year ago with the exact same issue, but nothing more recent. Do you have a link?

1

u/cforres May 06 '16

Yeah it's pretty misleading. Not to mention in the 1.x documentation, they have a somewhat well written page about the new component router that makes it seem like its ready to go.

1

u/bemlikanz May 06 '16

I don't know any of you feels like me, but I'm only sure and confident of using angular 2 in ionic2 apps.

1

u/dvidsilva May 06 '16

And maybe native script. That project looks great!

-2

u/onFilm May 06 '16

Even Angular1 supports SEO optimization that can easily be done within a day (prerender). Angular2 is a fucking mess indeed with the "solutions" it offers. I was about to make the switch the other day, but after checking it out was disappointed. Hopefully it evolves more gracefully than its release.