I hate to drag Go into this but I can't help but compare what happened here to the attitude here: https://github.com/golang/go/discussions/55092 https://github.

I hate to drag Go into this but I can't help but compare what happened here to the attitude here: https://github.com/golang/go/discussions/55092 https://github.com/golang/go/discussions/55092 My initial impression was that this is boiling the ocean but there's substantial foresight. If I'm blowing this out of proportion then the bar is already too close to the ground for my liking. This is solvable. I don't remember the last time a tool chain update broke my build. It's one thing if it's a bug fix. But for practically everyone to have to update? If 100,000 developers have to trip over this, say, then with your 10 minute estimate that equates to a million minutes, nearly 8 years at 40-hour weeks. This appears to be a problem totally worth solving.