Another place I see this is with the recent announcement from the Angular team stating there will be another major point release every six months. Like this is a bad thing?
And I look at that and honestly wonder why these people are programming in the first place. If change bothers you, you are really in the wrong industry.
I’m Moving To …
I seriously saw this comment on one of the articles announcing the major point release and jumping to version 4 instead of 3. The actual comment was, “I’m going to move to React.” Now, the reason he was going to move to React because he’s afraid that these major point releases are going to be drastically different from the previous version so that he’ll always need to be learning something new. I understand the fear. But, I think it is unfounded. Aside from the fact that the Angular team has assured us that there won’t be any breaking changes in the next version, what we have to take a look at is WHY there were so many breaking changes from version 1 to version 2.
Remember back to when AngularJS was first introduced? The best platform we had at the time was jQuery and KnockOut. Yes, there were others, but those were the most prominent. Especially jQuery. Since then, the browsers have stabilized and most of the reasons for using jQuery have vanished.
For any framework to stay stagnant under these conditions would be foolish, if not suicidal.
And to that programmer who is leaving Angular for React? Good luck. You think Angular is bad. React makes all those changes you dread without changing the major number.
What would it be like if …
Just imagine with me what it would be like if nothing ever changed. How far back do you want to go? How about back to where I started programming. OK, that was 29 years ago. I started programming on DOS 3.1 using Clipper (that’s a dBase III compiler). We had 640K (that’s 640,000 bytes, not megs, not gigs) to program in. We used overlay tricks to cram programs that were three times that size into the computer. There was no GUI and what graphics we did have were incredibly grainy. You were lucky if you had color. There was no Internet, that was still the “property” of the colleges and the universities. No Google to find answers to your questions. No blogs. No cell phones. No social media.
And all of that was less than 30 years ago.
And yet, the way many people act, they would like things to stay the same. And I ask, “Why?” So that 30 years from today we are still struggling with the same issues we are today?
Every new technology goes through essentially the same process.
At some point the new technology either dies, or matures enough that people start experimenting with how to use it best. This is the place where design patterns are developed and features are added to the language. This is the part of the cycle I love and is generally where I tend to jump into the technology.
Eventually the technology matures and gets boring. This is where I tend to jump off. Java and .NET are in this phase. The patterns for both are well established. What features are being added are at the “nice to have” level. But generally everything most people need to be able to do can already be done with what is available.
We are currently at the beginning of the experimental phase. Expect to see A LOT of change in the next several years. If you don’t like it, move to a more mature technology that won’t change so much on you.
The problem is, all the castles are now occupied by Kings and Queens instead of children who don’t know any better.
- WebForms vs MVC–The War Is Over - September 25th, 2014
- Create A Desktop Application using Angular, Bootstrap and C# - October 15th, 2015
- Are You Doing Angular Right? - November 5th, 2015
- Adventures Working With Angular’s $scope - November 26th, 2015
- Using Gulp to Bundle, Minify, and Cache-bust - January 28th, 2016
- Reactions to React JS and Associated Bits - March 17th, 2016
- An Explanation of the Flux Pattern - March 31st, 2016
- Ext JS 6 by Sencha - The Good, The Bad, The Ugly - April 7th, 2016
- Do This To Increase Your Client Side Web Development Speed - April 21st, 2016
- ES2015 Code Coverage and Jest (React JS Unit Testing) - May 5th, 2016
- 4 Reasons To Drop MVVM - July 27th, 2016
- You Can Start Using Node Today - August 2nd, 2016
- TypeScript and Electron The Right Way - September 6th, 2016