> Very much so, insofar as code written a few years ago probably doesn’t work anymore. Citation needed? Just a week ago I used a Python library completely unc

> Very much so, insofar as code written a few years ago probably doesn’t work anymore. Citation needed? Just a week ago I used a Python library completely unchanged from 2013. > Some of that comes down to libraries not being careful about versioning, but a lot of it is the language itself making seemingly random changes in direction every few years. "Seemingly random" is both wrong and insulting. The BDFL did step down and was replaced with a steering council, so maybe that's what you're seeing. I do agree that `match` was a bad addition to the language, but that's one small example among many supporting the opposite opinion. > 10 years ago: range 5 years ago: xrange Today: range again, LOL! Huh? Python 3.x has only ever had range(), so it's been range() for at least 10 years.