3 ms·
I'm glad to see official Google support confirmed, but I wasn't too worried about that. It's an open source project, always available on github at any version,
by andrewstuart2 12y ago
I'm glad to see official Google support confirmed, but I wasn't too worried about that. It's an open source project, always available on github at any version, and if Windows XP can survive this long without those provisions, then I'm sure Angular 1.x will be last a long time.
I think the one thing that I would change for Angular 2.0 is the project name. With so many of the framework elements being killed, and the whole thing rewritten from scratch on a different language (AtScript, compiled to JS), with a different API, with different paradigms, the name "Angular" and the expected meaning it's built up to all developers involved doesn't apply anymore.
I will soon need to update my resume to say that I'm experienced in Angular 1.x. I'll need to ask people developing projects built on Angular, "But which version do you use?" I'd say the same gripes apply to Python 2 vs Python 3.
I don't want to go all Romeo and Juliet on the name here, but maybe there's room for a semver 2.1 that specifies the hitherto-unspecified contracts you can expect to be upheld if a project keeps the same name.
- juleska 12y ago> I'm glad to see official Google support confirmed, but I wasn't too worried about that. It's an open source project, always available on github at any version, and if Windows XP can survive this long without those provisions, then I'm sure Angular 1.x will be last a long time. For example, I still using ExtJS 3.1.1 in some projects, even the 4.x version is available for a long time, so, i totally agree with you.
- cheriot 12y agoKeeping the name succinctly describes how 1.x will stop adding new features and the team behind it is building 2.0. It's a good move if the community stays with them.