Is it relevant anymore ? Most of the javascript developers I know are working with Ember.
Ember? I thought that died after react came out.
Angular 4.0.0 Now Available
11–20 of 360 posts
Re: Angular 4.0.0 Now Available
#12Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're interested in front-end at all. Happy to answer any questions! [0] https://docs.google.com/document/d/195L4WaDSoI_kkW094LlShH6g...
is it really smaller and faster. i got the impression the payload size reduction might come at a cost to render performance?
Re: Angular 4.0.0 Now Available
#13I suspect there's going to be a bit of pushback to this acceleration in numbering.
Major release every 6 months, 2 major version deprecation policy.
There was definitely some initial pushback, but we hope to demonstrate with this release that it's a) not that scary and b) good for both developers and users.
Most devs should see significant reduction (upwards of 50%) in their output builds. We think that's a reasonable trade off for a couple hours of work to upgrade.
In this release, most developers should be able to simply update their dependencies and rebuild. We're aiming for regular, planned, minimal changes, rather than Big Bang style change from AngularJS -> Angular.
Re: Angular 4.0.0 Now Available
#14Even 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
#15Is it relevant anymore ? Most of the javascript developers I know are working with Ember.
Ember? What the What? Isn't React the cool new kid on the block?
Re: Angular 4.0.0 Now Available
#16Angular core team here, we're pretty excited about this release. Main change, as noted, is the new View Engine. The design doc[0] is worth a read if you're interested in front-end at all. Happy to answer any questions! [0] https://docs.google.com/document/d/195L4WaDSoI_kkW094LlShH6g...
is it really smaller and faster. i got the impression the payload size reduction might come at a cost to render performance?
That's discussed in the doc (and there's some metrics). Update speed takes a (minimal) performance hit, in exchange for code size reductions.
We (and our colleagues at Google working on the web in general) find that the largest impact on performance comes from simply shipping less code.
Edit: correction: turns out our tests show we didn't take a perf hit on updates at all, and in fact ever-so-slightly improved. So win win :D
Re: Angular 4.0.0 Now Available
#17I'll probably try it.
But man, am I getting jaded about all this javascript framework stuff. Every 6 months stuff breaks, every 2 years there's a huge shift.
The problem with javascript I've been facing is value. Time and effort doesn't always correlate to what I get in the other end. In fact, I can say when building, going single-page is a time sink.
And it's almost always a mistake to go SPA first. Using a django or a rails lets you get the basics and data flow nailed down early on. Get into a framework too early and have a need to change something? Have fun explaining to your manager/client how costly it is to do a "simple" modification to a JS app when you have to throw the state you built it upon out the door.
What I want is a system tightly coupled into a server-side framework like a Django or a Rails that degrades gracefully and I only have to program the interactivity one time. Something that'd plop right into the asset pipeline/django compressor so I don't have to go outside of the framework to build.
Hundreds of hours of my life have been spent chasing this dream of sharing server side code with client side JS frameworks. That's what I need.
Meteor didn't do it for me. As for rendr, I've done stuff better with backbone/express in-house. As of 2017, I get my best bang for the buck using django and pjax. No joking, I went from full DRF + Backbone Marionette -> to plain old jquery and pjax and couldn't be happier.
All these new build tools (grunt, gulp, webpack... come on), ES versions (I was ok with ES5). None of these things are helping me ship stuff ahead of / on time and correctly. They're creating an even larger gap between the server side data, logic and templates and the JS interactivity.
If anyone is listening, I'd love to have a well-supported opinionated distribution of django or rails that just renders forms, tables, etc. with angular/react/etc. and degrades gracefully.
Re: Angular 4.0.0 Now Available
#18I suspect there's going to be a bit of pushback to this acceleration in numbering.
Major release every 6 months, 2 major version deprecation policy. There was definitely some initial pushback, but we hope to demonstrate with this release that it's a) not that scary and b) good for both developers and users. Most devs should see significant reduction (upwards of 50%) in their output builds. We think that's a reasonable trade off for a couple hours of work to upgrade. In this release, most developers…
I think you're right. Probably something similar to how they changed Java from the 1.x to the 5, 6, 7... series. It did take a couple years for people to stop saying 1.5 though, as I suspect will be the case for people saying "Angular2" trying to find a way to distance themselves from Angular 1 but not really caring if some component was written for 4, 5, etc..
Re: Angular 4.0.0 Now Available
#19Even 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?
Most developers should be able to simply update their dependencies and rebuild. A few APIs have been deprecated, but they continue to exist and can be removed at a developer's leisure, per our versioning policy [0]
http://angularjs.blogspot.com/2016/10/versioning-and-releasi...