The real complaint right now should be Babel v7 -- or more specifically, the community around it. Babel v7 has been in development for quite a while. It's still

The real complaint right now should be Babel v7 -- or more specifically, the community around it. Babel v7 has been in development for quite a while. It's still changing and isn't even a RC yet. I understand the need to test new compiler builds, but production isn't the place to do that (especially not until a RC is released). A beta designation is meaningless if its used as though it were just a normal production release. Using a beta compiler in production tools, libraries, etc shows EXTREME inexperience. I have a number of dependencies that I cannot update because the new versions rely on various v7 builds (ranging from ancient alphas to bleeding edge betas). I suspect the issue is that most JS dev teams are small with projects small enough that edge cases are uncommon and easier to find and fix. Stackoverflow dev survey shows that the average US dev is 28.7 (down from 31.6 in 2015) with an average of 10 years of experience despite 58% having less than 5 years of experience. That means that on average, you have a very young team. Further, the vast majority of teams most likely do not have ANYONE with more than 5 years behind them. It's not surprising that such things aren't recognized for the disaster-in-the-making that they are. Web technologies have settled down and stabilized dramatically over the past 3 years. I suspect that as more web devs gain more experience, we'll see this continue as rashness is replaced with a more conservative approach.