31–40 of 360 posts
I am seeing : platform-browser / platform-server namespace. Can we expect platform-android, platform-ios, platform-jvm ?
Looking at the angular compiler pipeline, with AST this should be possible ?
Just a quick note to those who would like to play around with it.. Install the latest version of the CLI: npm install -g @angular/cli And then run: ng new project-name --ng4 The "--ng4" flag is currently required, as it doesn't yet install ng4 by default.
Edit: it's released! npm install @angular/cli
Congratulations to the team. I have been using Angular 2 for our internal operations dashboard. I am seeing : platform-browser / platform-server namespace. Can we expect platform-android, platform-ios, platform-jvm ? Looking at the angular compiler pipeline, with AST this should be possible ?
The last one, well, that's a bit more complicated. Let's just say that sort of thing is on the radar.
Earlier quoted context omitted.
I think Typescript can sometime have a mind of its own, but it's certainly an enrichment and with Rx everything just falls into place. At this point it's hard to ignore that all the UI libraries are just paradigms and patterns, and how we use them is getting less important. These days I just want to write Component-style UI code, and I'll be fine. Similarl things can be said about RxJS, but I think since it's a diffe…
We've got some really cool ideas to make Rx really first class in Angular. It's already pretty deeply integrated, but with a little work, it'll be awesome.
Community here has been pretty negative on this lately. So I'll just add I've been using Angular 2x and also Ionic 2 the last year or so with great success. One real benefit we saw was the ability to take a lot of Backbone code and just quickly port it (models to services, templates just back to html for a component, etc). This is helping us help our enterprise clients in conversions of both older front end code and…
I suspect there's going to be a bit of pushback to this acceleration in numbering.
If my experience is any indication of general industry practices, businesses are very risk averse when it comes to upgrading libraries or dependencies as it usually triggers costly regression testing. At my current gig, we still run on angular 1.3.something and there is no way the business will allow us to migrate to v2 as we struggle to justify exactly what added value will we get from essentially a top-down rewrite…
We as engineers should not accept this. Business should not be involved in technical decisions like library upgrades. Business and engineering should negotiation development scheduling, nothing more. This means what new features are worked on, what bugs are prioritized, etc. All remaining time should be up to engineering's discretion.
And if business has you working on features full-time, then that's a (really) bad business and you should find a more acceptable company to work for.
in 2017 I'm curious why I'd pick angular over vue for a web-based project, if anyone has insight. not over "x js framework" -- over vue specifically. vue 2 is pretty much exactly what I wanted angular 2 to be.
Earlier quoted context omitted.
I'm actually really excited about Angular "2+" for something you've expressed here. I know that a React developer won't see this the same way, but I really feel like it's come down (for me at least) to either Angular "2+" or React - and whatever the reason someone is going to be on one side of the fence or the other. I've written smallish to largish programs in Vue, React, Ember, Polymer - and in all of those cases t…
Didn't GWT provide you with type checking on the frontend 10 years back ? Still works, incidentally.