One problem with not changing at all for a long time is that everybody forgets what it means to change. Teams stop planning for it, developers get too used for

One problem with not changing at all for a long time is that everybody forgets what it means to change. Teams stop planning for it, developers get too used for things being they way they got to know over the years. Then you get huge pills like Java 8 which took forever to be adopted in large corporations. I have witnessed most of Java history play out, starting with Java 1.3 in 2000. Looking back, I wish we had regular change cadence where new features are being slowly added at a regular pace so the versions don't feel like a completely new language and developers have time to digest the new possibilities. It is interesting when you spend multiple years on various projects, each being in a state of migrating from 1.6 to 8. Or coming to interviews and the first question being asked is "Which version of Java are you working on right now?".