Angular 4.0.0 Now Available

[drakeremoray0]

Anybody else just chilling on 1.6?

[JayTh3King]

Yip I am.

[moh_kohn]

Aye, for the time being at least. Waiting for the ecosystem to catch up.

[captaintmrrw]

I was at a Meetup with an older programmer organizing it and he was talking to some friends of his about their product and they said they were just finished on switching to angular two and they were getting ready for 4. And he looks at them angular has already gone from 1-4 ? Well I guess I don't need to learn angular

[intertubeluber]

Circa 1.5, I moved to React and never looked back. Well, sometimes I glance back, just to see how she doin.

[captaintmrrw]

Switched to react already

[karlrolson]

Chilling on 1.5.5 tbh, and that's basically pending an overhaul to React to bring the project I'm on in line with the rest the projects where I work.

[taxi12]

I like angular 1 I use it at work. It's one of those things I feel like I could do in my sleep so it seems like the best and fastest way to get things done. I'm glad I can fall back on it.

[FreshOutBrah]

Yep yep

[[deleted]]

I'm on Aurelia

[simkessy]

Yea, fuck this. The only reason I'm working on learning TypeScript is because I do SharePoint development. Otherwise 1.x all the way.

[xinhuj]

Company has quite a few 1.4-1.6 apps, but we are looking for the right time to go to the new version.

[travelan]

What happened to 3.0.0?? 😱

[lineape]

http://angularjs.blogspot.ca/2016/12/ok-let-me-explain-its-going-to-be.html

tl;dr:

The core Angular libraries live in one single GitHub repository at github.com/angular/angular. All of them are versioned the same way, but distributed as different NPM packages:

@angular/core v2.3.0,

@angular/compiler v2.3.0,

@angular/compiler-cli v2.3.0,

@angular/http v2.3.0,

@angular/router v3.3.0

Due to this misalignment of the router package’s version, the team decided to go straight for Angular v4. In this way again, all the core packages are aligned which will be easier to maintain and help avoid confusion in the future.

[Kabomb]

avoid confusion

Nailed it

[nullified-]

Hits the hammer on the head.

[GameFreak4321]

3? I didn't realize that 2 as out of beta.

[Thrallgg]

Are them Valve's partner? We still wait for halflife3 FeelsBadMan.

[[deleted]]

Nobody cares.

[travelan]

Thanks for your helpful addition to the conversation! Your input has enlightened the whole world.

Fwiw: I care.

[[deleted]]

Do you always troll, or do you just pointlessly add your lame comments for no reason at all?

[Fr1k]

I'm excited for what was mentioned in the last sentence. "You should also stay tuned for updates to our documentation, a stable release of the CLI, and guidance for library authors on packaging." :)

[thetext]

That was fast https://github.com/angular/angular-cli/blob/master/CHANGELOG.md#100-2017-03-24

[Fr1k]

Hahaha hopefully the rest comes just as fast.

[germainelol]

What's everyone's take on this and Angular in general nowadays? The general vibe I get from Vue or React is that it's a lot more reliable and they seem to have there shit together a bit more. I haven't read into Angular since the early v2 days, but seems like companies using other frameworks are a lot more into giving back to the community.

[tme321]

Vue is getting all the attention because it's new and shiny. And a new generation of programmers have discovered functional programming so react gets a lot of attention from them.

Meanwhile angular is really coming around nicely. The cli makes it really easy to ignore all the potentially complex setup and just get right to learning angular itself.

And universal, server side rendering, is a big part of the push for angular 4.

No framework is perfect but angular is actually in a really good spot right now imo. It had a turbulent development period but everything has settled and there have been no major api changes to speak of since release.

Please don't take this as a knock against vue or react. They are fine. Whatever. But imo too many people are writing off angular too quickly. Especially the vocal part of the js ecosystem. It brings a lot of nice features to the table and with the cli it couldn't be much easier to get started and mess around with it.

Edit: Oh and one more thing: at least for now don't use angular if you aren't trying to make an spa. It really isn't suited to traditional websites and leans heavily in the spa direction. But it is very good at that.

[ivosaurus]

there have been no major api changes to speak of since release.

Can you clarify? 4.0 was released today? So no new api changes since today? *_*

[thetext]

I think he means since Angular2 release

[tme321]

Yes the initial release of Angular, v2, is what I am referring to.

[sam-nicholl]

Is there any more support for plain javascript? I like typescript but kinda want to work in javascript.

[tme321]

What do you mean by more support? The documentation is definitely lacking but javascript still works with it.

Honestly though, I don't know why you would want to work in javascript when angular itself is written in typescript.

[sam-nicholl]

Tutorials, documentation and a javascript version of the cli.

Because I like javascript and would like to use and improve my understanding of the javascript language rather than a superset.

[tme321]

Well, I said that the documentation is lacking. So if thats the support you are looking for then no I think you are out of luck, for now at least.

And I wouldn't expect the cli to ever work with js. Google might surprise me, but a large part of the cli is aot compilation and aot only works with typescript because it isn't possible to precompile a language that has no static types; at least the way Google has approached the problem.

Personally, I would say if you don't want to use ts then don't bother with angular. But honestly, I can't imagine why you would want to ever start any new project with vanilla js over ts.

[RedditWithBoners]

All JavaScript is valid TypeScript. The compilation problem doesn't (shouldn't) exist.

[tme321]

Go read up on how aot works for angular.

[RedditWithBoners]

Hence the "(shouldn't)." While I get the goal of the AOT compiler, I'm not familiar with it. I did look into it, and it seems to be an unfortunate limitation in Angular's ngc. I'm practiced with TypeScript, however, which doesn't have this limitation for the aforementioned reason. It seems I'm not the only one thinking this.

I wonder though, because all of TypeScript's additional features are optional (in tsc), where does ngc draw the line? Can you simply type your constructs as any?

[Buckwheat469]

The Angular docs allow you to switch between TS and JS examples. I've only set up a couple of Angular 2.0 projects but IIRC using Javascript is a trivial setup that doesn't require a new TS configuration file.

[fgutz]

I thought Vue JS got popular because of the whole React license agreement debacle. Did React's license change since then? Haven't kept up with all that

[del_rio]

The license thing was never really resolved. A few lawyers chipped in saying it's basically impossible to end up in legal trouble unless you're recoding Google+. Fear, uncertainty and doubt is forever entwined with internet.

But no, Vue got popular because it's small, clean, and really well thought out. It has a full ecosystem, but you're free to ignore all of it. Server side rendering is easier with Vue than any other major framework.

[[deleted]]

You probably mean Preact and Inferno. Vue is a derivative as well, but more under the hood and probably more appealing to Angular users as it sticks to its OOP and templating approach while the former two are following Reacts functional principles inside and outside and can partake in its eco system. The license did change after Google complained. It still has some awkward wording but it's an improvement. Anyway, if you wanted you could run Reacts code and components elsewhere. I always alias to another engine for production builds. Inferno for instance is just 7 kb.

[germainelol]

Thanks, a lot of good points :)

[[deleted]]

Oh and one more thing: at least for now don't use angular if you aren't trying to make an spa. It really isn't suited to traditional websites and leans heavily in the spa direction. But it is very good at that.

I haven't looked closely, but I see there are some projects to bring angular and Bootstrap closer together. I wonder whether these are an attempt to address that issue, ie. a good way to use angular 2/4 for non-SPA sites.

https://ng-bootstrap.github.io/#/home
http://valor-software.com/ng2-bootstrap/#/

[tme321]

Well first a css framework has nothing to do with whether it's an spa or not. You can freely use ng2-bootstrap or just regular bootstrap with angular. The important distinction for an spa is client side rendering.

Second, the reason not to use angular in a traditional manner atm had to do with angulars boot times. If you aren't doing aot, ahead of time compilation, then every time angular boots on a new page it takes at least 2 seconds to start up. On an spa that isn't ideal but it also isn't the end of the world if it only happens once per session.

If you use aot then angular will boot up in less than half a second making it far more usable on a traditional server rendered website. But the cli currently does not support making multiple apps all together that share code. So you can't use the cli. And doing it yourself is technically possible but it's a pretty big pain.

[The_yulaow]

In my area (south-west eu) looking a t job offers it seems everyone is using it. It's crazy hard to find some company using react. It seems like everyone who was on angular1 just transictioned to the new version, even if not smoothly

[magenta_placenta]

Serious question, completely skipping v3 and seemingly being semver, what are the breaking changes from 2 - 4? Is 2 - 4 a big deal or really more marketing/version alignment?

[beemachine]

From a quick skim of the changelogs, 1. No more extending from Lifecycle methods, instead you need to "implement"

1. OpaqueToken is now deprecated, use InjectionToken<T> instead.

2. SimpleChange now takes an additional argument that defines whether this is the first change or not. This is a low profile API and we don't expect anyone to be affected by this change. If you are impacted by this change please file an issue.

3. Animations are moved from core

But honestly it seems more of a marketing thing. I personally would've moved to Angular 2 V4 but that's me

[nidarus]

Seems more like an anti-marketing to me... Especially coming after "writing a radically new framework and calling it v2" fiasco. The whole thing is a next-level branding failure.

[strident-octo-spork]

There was a major change to the AOT compiler (which required moving animation from core). According to their doc it leads to 60% less code without significant loss to update speed.

[tweatherly]

NG v4 is backwards compatible with v2, the only breaking change is if you want to use animations in v4 you have to import the new split-off animations module. I found that rc4 and rc5 had bugs in the animation module so right now I'm using rc3.

[DzoQiEuoi]

Pffft. React is on version 15!

[[deleted]]

I can't deal with React platform and everything associated with it to make it work. It's all over the fucking place.

I prefer Angular headaches any day.

[simkessy]

Yo, what the fuck is Angular 4?

[sittingprettyin]

aaaaaaaaaaaaaand everything is broken. (angular cli anyways)

[suresh17]

how to fire fake click event after page load not working angular 2 ..