ANGULAR 2 - Anyone using this?

Hello, webdevs,

Is anyone here using Angular 2 yet? NEETs need not apply, I want to know of anyone is using this over engineered BS at their day job, in production.

Other urls found in this thread:

infoq.com/news/2016/12/angular-4
twitter.com/NSFWRedditImage

Not really. 500KB just for the library? 4 seconds to bootstrap applications?

No fucking way. Going full Polymer 2.0 when that releases. For now, jQuery / vanilla.

don't use it. they're already coming out with version 3

why is front end such a mess, fuck

>new version twice a year
Jesus fucking Christ

We are still using Angular 1 for a huge project. I asked the project lead if he thought about upgrading to Angular 2. He said they looked into it, but the releases are constantly broken and not worth the risk.

angular is a great case study on how to kill a popular web framework

NIH, mostly.

>new version!
>breaks all compatibility with old version
>also old version is out of support
>we're gonna keep releasing like this, nothing is wrong

Angular earned a place on my "never" list the moment Angular 2 was announced.

Oh wait, no, it was before that, when they decided they'd come up with new hipster names for design paradigms that have existed for years.

Fuck angular, I will never work at your company if you use it. React + Redux is great.

Yes, but it's semantic versioning.
They're not going to do major changes or rewrites, major versions jus show that there will be some breaking changes.

Going from Angular 2 --> 4

infoq.com/news/2016/12/angular-4

>React + Redux is great.
whats a good place to learn it for retards like me? I just want to move a shitty jquery site to something more modern

Waste of time.

You're far better spending time learning the 24 GANG-OF-FOUR Javascript Design Patterns and mastering them.

t. Vlissides

Well I'm more a c# mvc type of guy... Never trust this fads that fade away

+1 to this.

I can't believe Pajeets falling for these memes yet they can't even use a time-tested Design Pattern to solve their simple shit.

>Pajeet: How do I output the remainder of 5?
>Sanjay: Use angularjs for that!
>Pajeet: Really?
>Sanjay: Yeah, and use jQuery to style the appearance, because, you know, clients like to see it beautifully styled, so use jCurry as well

t. Erich Gamma

>tfw my boss kept asking why we aren't using a framework like angular
>I send him a link to the angular google group around the angular 2 releases
>"oh"
>he never mentions it again

at first sight the typescript environment seemed like a nice place to start, until you try to build your project and one of the dependencies breaks either because the version of the ts transpiller is incompatible with the daily version of angular2 or the remaining requirements is. good luck finding what the problem is and solving the "requirements loops" when all that "final" js code is nowhere near what you just wrote and youll have to manually "backtrace" every action the transpiller made and debug that shit
not to mention that i fucking hate node with a passion, that shit needs 20 seconds after a build process has finished to reload another node "process" just to show a success/failure message
fuck that shit, almost costed me a job, aint ever touching that shit again (v1.x is fine though, only one js file needed and simple to manage dependencies: just include them ffs)
/rant

No, but we're using Angular 1 for some projects.

>2014 + 3y - 7d
>not using EmberJS

I used it for a software engineer degree project.

The biggest problem, as others mentioned, were that the Angular team made gigantic fucking changes every week while it was in beta and RC. Thus keeping up with bugfixes (which was necessary due to how certain bugs broke shit in other browsers) for six months was a pain in the fucking ass.

Now that it finally is stable, it can be used properly. Developing websites with it was completely fine and dandy. Using lifecycle hooks, pipes, modules, how the routing was handled and such was really nice to work with. Though normal Angular could give most of these features too. Though the performance was excellent.

TypeScript was also really nice. If Microshit needs to be given a pat on the back, this would be it. Then they can go fuck themselves over their half-assed piece of shit integration with NPM and Angular.

So all in all, it was fine. But keeping the house of cards that was Angular 2.0 standing was a bigger chore than using the actual API. Fuck me we had so many fucking problems with it breaking that maintaining the fucking dev environment was a more important task than writing the damn code. Maybe shit has changed now that it is stable.

>not using vue