r/angularjs • u/burczu • Nov 11 '16
Please stop worrying about Angular 3
https://toddmotto.com/please-stop-worrying-about-angular-34
6
Nov 11 '16
I mean, Google destroyed any meaning of the term release candidate, so why not re-write what "version" means as well?
12
Nov 11 '16
Google destroyed any meaning of the term release candidate
I think React did that by jumping from v**.**14 to v15.
3
3
Nov 11 '16
Angular 1.x cannot be compiled into native code
That's the only mention of this in the article. I'm not aware that this is a planned feature of Angular 2/3/4. Is It?
4
u/toddmotto Nov 12 '16
Check out NativeScript, it's free and open source. Write Angular 2 apps, it'll compile down to native code: http://nativescript.org
2
u/immigrantnightclub Nov 12 '16
This article talks about the render service and the DOM abstraction:
https://medium.com/@NetanelBasal/angular-2-explore-the-renderer-service-e43ef673b26c#.ypujnp4sw
-3
u/FriesWithThat Nov 12 '16
Don't worry about it.
4
Nov 12 '16
Gee, that's really helpful.
-2
u/FriesWithThat Nov 12 '16
Did you read the title of this submission, or have a sense of humor? Never mind.
8
Nov 12 '16
Did you read my comment asking for clarification? Sorry, I don't care about your attempt at humor. This is what I hate most about reddit - always going for the joke/meme/movie quote/etc, and it usually gets upvoted to the top.
1
Nov 14 '16
What I don't fully follow from all of this, as a newbie web dev, is what it will mean if I don't upgrade every year? Will the deprecated api still be supported or am I hosed? I don't want to build on a framework that requires me to upgrade every year, frankly.
10
u/argues_too_much Nov 12 '16 edited Nov 12 '16
pre-note: I wish I'd been more eloquent in my first comment that it seems prompted this and I worry it's now beating a dead horse but I hope it's going to be seen as constructive feedback.
For me when I ranted so horribly in that thread it wasn't about version numbering in itself, or learning a whole new framework/concept, so much as what major versions signal.
Semver exists because it gives developers an idea of how big changes might be. Major versions are breaking API changes as the post mentioned. Minor versions could be new functionality. E.g. adding Components as happened in 1.5 could under the new numbering system have been a minor version as they didn't impact existing APIs (at least not in my experience using 1.5 so far).
To me it's not worth as much when framework developers say "ok then, what we'll do is have a major release every 6 months, developers will expect breaking changes from one release to another!".
That's true, and fair, but it doesn't help me that much when selecting a technology. What it's doing is telling me that if I want to keep my applications up to date I have to set aside an unknown amount of time every 6 months to fix any breakage.
The semver website even indirectly discusses this in the FAQ:
From the post on this you said:
As good as that sounds it still leaves open questions. Maybe they're unfounded and I hope they are, but I'm wary having used other technologies which have dragged me into the upgrade rabbit hole and caused long nights.
How much time? It's said information will be given on changes, but how can I estimate that now before I choose the next generation of technology we use? The unknown is the worry. The changes could potentially be enormous even if they haven't with the older non-semver setup before.
Someone in the comments said don't upgrade. That's not always an option, e.g. if there's a bugfix that we hit that can't be backported for architectural reasons then I have to upgrade. Or, if we don't upgrade for 3 major versions? Expect even greater changes and even less of a clear idea of how long they might take. Especially for larger applications.
What I would love to see is fewer major versions, keeping a stable API, with regular minor version updates which have new functionality and features above that base. E.g. They add Components, it gets bumped to 2.5 from 2.4.
I know other frameworks are doing it the same way as Angular is planning, but that doesn't encourage me to use them. The concerns would still be the same. Hah, this would even be an advantage to Angular for me if they're all doing that!
I know everyone's busting their asses to move things forward, but that has its own pains, and it's not restricted to any specific frameworks.
Anyway, this was supposed to be a shorter second version of why I still worry, but it hasn't worked out that way! I'm already dreading any conversation that's about to start. I'm aiming for this to be the last time I post on this topic. Lets see if that happens! Anyway, Thanks /u/toddmotto for creating this post and Angular devs for busting their asses!
Edit: also, I said in the last post in discussion with Rob Wormwald who politely responded to my late night ranting that I'd wait and see if my fears are unfounded, and that's still the case, maybe everything will be fine.
tl;dr erm, so, them cubs eh?