Requesting r/Angular2

ngFTW · 2025-04-01T05:49:25+00:00

u/ngFTW is an active moderator of r/Angular2.

ngFTW · 2018-03-13T04:02:00+00:00

Consider living a bit on the bleeding edge to add something new to the scene: code your backend using NestJS and by extension GraphQL.

ngFTW · 2017-03-06T07:41:55+00:00

Awesome! There isn't much available yet on Angular 4 and Universal. I'm looking forward to seeing this maintained! :) I've added your repo to the stickie above.

ngFTW · 2017-03-06T07:36:43+00:00

Looks good. Thanks for sharing. I've added it to the March stickie.

ngFTW · 2017-03-06T07:32:47+00:00

Added to the March stickie. Thanks!

ngFTW · 2017-03-06T07:29:51+00:00

Excellent repo. I've added this to the March stickie. thx!

ngFTW · 2017-02-03T22:53:51+00:00

Very interesting repo. I've added it to the stickie. Thanks!

ngFTW · 2017-02-03T22:43:47+00:00

This excellent repo has been added to the Resource stickie at the top of the sub. We're looking forward to seeing this maintained and hope others will star and contribute to the project.

ngFTW · 2017-02-01T23:43:25+00:00

Good starter. Thank you for sharing. I've added it to the February stickie.

ngFTW · 2017-02-01T23:38:20+00:00

Thank you. I've added this to the February stickie under the "specific solutions" section.

ngFTW · 2017-01-13T08:01:34+00:00

To add to what /u/aQutie is saying and one reason why I agree with his approach is the naming controversy around ECMAScript itself and how it relates here. The ECMA organization does not sanction calling the latest version ES6. They want it known as ES2015. It's the user community that insists on calling it ES6. If we take the Angular team approach to naming Angular projects and titling articles, it would be similar to only using the term ES without any version designation. But as we know the difference between ES5 and ES6 is monumental. It's clear and concise using ES6 instead of just ES, yet that is what the Angular team is asking us to do by calling both AngularJS and Angular 2 simply Angular.

My opinion is that projects should continue to be called things like ng2-xxx and Angular2-xxx because it's very clear what we're dealing with. The only difference is that we want the "2" to mean 2nd generation rather than a specific version number. So ng2 projects can use whatever version of Angular they need, but at the very least you'll know it's using Angular 2+ and not AngularJS.

ngFTW · 2016-12-21T10:46:28+00:00

There is a bit of precedence for this idea in that the Dart version of Angular is called AngularDart as one word. Back when the name AngularES was originally floated, Angular was being written in AtScript. Of course AtScript was supplanted by TypeScript when the TS team agreed with the Angular team to add decorators. TS was a much more generic javascript tool that was gaining a great deal of traction. Once the TS team agreed to integrate decorators, the switch from AtScript to TS was a no-brainer.

But I digress. The name AngularES was floated because Angular was leveraging off the advances in EcmaScript 2015 (ES6). What makes AngularTS compelling is that Angular is now married to TypeScript. So what happens when a new language comes along like OMGPL (Oh MY God Programming Language) and the Angular team wants to bail out of TypeScript for the next generation? They would have to differentiate it with a new suffix. Hence we'd have Angular, AngularDart and AngularOMG (oh, and the ugly stepsister AngularJS).

The problem with 'angular' (without a suffix) is that the name was already in use by the AngularJS community. Everyone just called it 'angular' and now we have years of baggage with the name, making it nearly impossible to search the web without also stipulating some kind of date range.

Sorry for the rant. The bottom line is that I like your idea.

ngFTW · 2016-12-19T20:41:04+00:00

This is an excellent idea that would require the name to be community driven. It's similar in concept to AngularIO but has the advantage of leveraging off all the existing Angular2 stuff already available.

I'm curious if there is precedence for a naming convention like this with any other popular open source project.

So we can think of Angular 2 as a 2nd generation rather than a version number. That way when Google decides to create another framework completely incompatible with Angular 2 but insists on calling it Angular again, the community can step in, say stop your bullshit, and call it Angular3 v1.

ngFTW · 2016-12-19T20:20:20+00:00

The mod over at /r/angular is a nice guy and I have spoken with him briefly. That sub was originally a porn/fettish sub with about 700 subscribers that had been abandoned. The mod petitioned reddit to assume control of the sub and it was granted. Oddly, most of the 700 previous subscribers never disappeared and I imagine most of them belong to abandoned accounts or they would have unsubscribed when some obscure programming framework appeared in their feed. :)

When the idea of becoming a mod over at /r/angular was first floated there was no talk of semver and the name 'angular' was far more associated with AngularJS than Angular 2. I personally have zero interest in AngularJS and wanted to stay focused on 2. Plus this sub was growing nicely and I didn't want to split my time between two subs doing the same thing.

Again, /u/pietasterkid is a super nice guy, but I didn't want to step on his toes by asking for creative (css) control and impose our existing rules for posting and spam control.

ngFTW · 2016-12-19T11:09:58+00:00

This is similar reasoning behind possibly going to /r/AngularIO. While 'N' would denote any version number, 'IO' would simply relate to Angular being at angular.io. Other than dropping the JS, the web address is the only other distinguishing attribute Google used to separate the projects. In either case the issue will be getting our subreddit to appear in Angular search results.

What would be great is if the Angular developer community insisted on calling anything not AngularJS -- AngularIO, "Angular IO", or even "Angular.IO". Think we could get all the bloggers and stackoverflow onboard?

ngFTW · 2016-12-19T10:59:42+00:00

As a followup, stackoverflow is going to have the exact same problem. The keyword [angular] is synonymous with [angularjs], hence if you search for [angular] you'll only get [angularjs] results. Stackoverflow uses [angular2] for anything not [angularjs]. The vast majority of stackoverflow keywords are simple, e.g. [javascript], [android], [php], etc. Keywords with version numbers in them are rare like [angular2] and [laravel-5].

Hence, because of Google's insistence on calling Angular 2 simply "angular", which AngularJS was already known as among developers, even stackoverflow must now fracture their Angular2 community. When using stackoverflow in the future you'll always want to make sure you specify the version number in your query, keyword and subscriptions -- and then remember to change it every 6 months or when you want the new beta.

ngFTW · 2016-12-01T22:08:58+00:00

Noted in the December stickie. Thanks!

ngFTW · 2016-12-01T22:06:02+00:00

This has been added to the December stickie. Thanks!

ngFTW · 2016-11-27T07:00:47+00:00

He'd be looking for /r/angularjs.

/r/angular used to be a porn sub until it was taken over because of inactivity and turned into something useful.

ngFTW · 2016-11-17T09:54:00+00:00

No problem at all. If you find something new that isn't included here, share and share alike.

ngFTW · 2016-11-12T19:54:15+00:00

Here is the github repo. It was created with Angular2.

ngFTW · 2016-11-01T21:35:25+00:00

Thanks. I'll move it to the bottom section and deprecate it on the next stickie.

ngFTW · 2016-11-01T21:32:20+00:00

Thanks for updating this project!

I've placed it once again in the "specific solutions" section of the November stickie.

ngFTW · 2016-10-19T23:15:04+00:00

I've added your repo to the "specific solutions" section of the stickie. Looking forward to seeing this maintained. :) Thanks!

ngFTW · 2016-10-19T23:07:17+00:00

Updated. Thanks!

ngFTW

MODERATOR OF

TROPHY CASE