Have you met a person who has more than a year of experience with the Angular 2 framework? Already. I'll tell you how I got there.
In early 2015, I finished working on the second edition of my book on Java and, as usual, I said to myself: "Never Again!" Working on a programming book is quite exhausting, and after nine months, you usually want to push out this next child.
A couple of months I got a call from the editor of the Manning edition and began to wonder what I was doing and whether I wanted to write a book. Yeah, right! I began to languidly support the conversation and said that I do not want to write about Java, but now I'm working on Web frameworks. The fact is that for the last three years our company has been trying to find a substitute for a framework that requires a disgraced Flash Player.
It should be noted that at that time on the Internet there were rumors that Google decided to completely rewrite AngularJS, and that the new version would be called Angular 2. In short, I suggested my colleague Anton Moiseev to co-author a book on Angular 2, that is, write a book about , Which is not yet, and he agreed. After a year of work, the book is ready, and Angular 2 1.0 is about to see the light.
As ham and hamster
But today I would like to talk not about the technical merits of this really cool framework, but about how Angular 2 is sold and released for us.
If Microsoft had used the same marketing strategy, they would not have named a fairly new TypeScript language, but would promote it as C # 2. Both of these languages were coined by an author named Anders Hejlsberg, right? Then they would publish a migration guide from C # to C # 2, which would be just as eager as the migration manual from AngularJS to Angular 2. I'm sure next year there will be new tutorials explaining how to migrate to Angular Applications from React, Ember and ExtJS, and these processes will not be more difficult than migrating from AngularJS to Angular 2.
Okay, stop nicking the name of the framework. Let's move on to the release versions. For the book, we wrote a lot of small applications, and we had to rewrite them for each new alpha release of Angular 2. We did not complain because we knew what we were signing. In each alpha, there were breaking changes, and we copied all the examples once in 20. At the beginning of 2016, the framework went into beta, and in May 2016 the joyful news came: Angular 2 Release Candidate 1.
When I was asked in January, is not it risky to start developing a new web application with Angular 2, I confidently answered "Yes, the framework is fairly stable". I was wrong! In my professional life, I've seen many releases and I was sure that alpha always includes new features and breaking APIs. Beta is for bug fixing, and release candidates are for polishing the product. Who would have thought that in the period between RC.1 and RC.5 and Router the APIs and Forms APIs would be completely rewritten, and a completely new API for the modules would change both the internal architecture of the framework and the loading of applications?
If you ask me today (at the end of August 2016), it's safe to start developing a new application on the second Angulyar, I'll answer this: "If Angular 2.0 is not released in September 2016, do not do it."
Go to StackOverflow, and you will see questions like: "I have such a problem. I'm using Angular 2 RC.1. " If someone suggests an upgrade to RC.5, the author of the question will write "I do not have time for this".
And is an upgrade from one RC to another one a multi-step process? Can! Even the manual for the upgrade from RC4 to RC5 is. And the subtitle is hearty: "Migrate your RC4 app to RC5 in minutes." Yes, tell me. This is what I am now doing. It took me a week to translate 40 small applications from RC.4 to RC.5.
From the recent Adventures in Angular podcast, I learned that when Angular 2 developers decide whether to include breaking changes in the next RC, they ask themselves the question: "Does this improve Angular?" If the answer is "yes", then they take a crowbar in their hands ...
Mikhail Zhvanetsky once said: "What does borsch have to do with such things in the kitchen!" Dear developers of the second Angulyar, I like Angular 2 RC.5 as it is. Please take up bugs and stop adding new ingredients to borsch! Very much to eat hotstsa! Give us a stable release and take it out for six months - we also want to release our applications.
The happy ending
Do not forget about 15 million Java and .Net developers, most of whom have not yet touched Angular 2, and when they touch, they will like it!
At the end of September, the AngularConnect 2016 conference will be held in London, and I very much hope that someone will come to the podium and say: "Ladies and Gentlemen! We have the most pleasant news for you. Today went out Angular 2 1.0 ".
In 2017 headhunters will run for developers who know Angular 2. Prepare a sleigh in the summer, if you know what I mean.