ruby and python – why all this versioning nonsense?

I like the ruby and python programming languages because of their simplicity. Sometimes it feels like I’m cheating, with all those built-in functions. But there is one terrible flaw to both of these – versioning. My software is versioned, but my programming language should be stable. I shouldn’t have to juggle multiple versions of Ruby just to support applications that were written at different times. I suppose an end-user launcher can handle all of this on it’s own by configuring the runtime env at installation or launch. The user doesn’t need to install a version manager and keep track of what version every application needs.

When Java comes out with a new version, do I need to run some workaround tool like “jenv” to install the new version while preverving old ones? Java doesn’t make us do this. Neither do C or C++, although of course the latter two aren’t obsessed with constantly rolling out new versions. Agile sucks bad enough as a software development workflow. Infecting the languages with this Agile nonsense is asinine.