Looks like cool features, but I have a hard time envisioning on how they all work together.
Angular 4.0.0 Now Available
41–50 of 360 posts
Re: Angular 4.0.0 Now Available
#42Re: Angular 4.0.0 Now Available
#43Re: Angular 4.0.0 Now Available
#44Does anyone have an good example app using modern Angular? Looks like cool features, but I have a hard time envisioning on how they all work together.
Re: Angular 4.0.0 Now Available
#45Re: Angular 4.0.0 Now Available
#46Is Angular ever going to support web standards such as web components?
We also support native (or emulated) Shadow DOM out of the box.
It gets a little more interesting when you start interleaving Angular and WebComponents, but one of the deprecations in 4.0 (regarding Angular's use of the tag) is squarely aimed at making that easier in the future.
Re: Angular 4.0.0 Now Available
#47Even with SemVer versions it looks really weird to see a new Angular relase branded as 4.0.0. Angular 1 to Angular 2 made me drop angular entirely, that happened less than 6 months ago I believe. Just reading Angular 4 gives me the creeps. Is 4 widely different from 2? How am I suppose to know if you using semver and already have a really bad history?
Re: Angular 4.0.0 Now Available
#48Re: Angular 4.0.0 Now Available
#49Earlier 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.
Re: Angular 4.0.0 Now Available
#50Earlier quoted context omitted.
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…
> there is no way the business will allow us to migrate to v2 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 y…