GeezerVison

so while this seems to work it sort of doesn't fit nicely with pre-commit. normally language_version support means that pre-commit will install the particular programming language version into the pre-commit environment such that there's no "external" dependencies on the host itself (in the docs this is referred to as first class language support). I believe this patch doesn't do that -- it instead relies on an external version manager to keep that in sync and so it doesn't fit the same properties as pre-commit does today.

basically for actual language_version support one should be able to pick up the pre-commit cache and drop it on a relatively-similar empty operating system and still have it work (for first class language support)

if I understand correctly language: rust does a similar approach (rustup vs juliaup) and maybe the approach there can be copied here?

I did see (and was surprised) that rust installs an entire tool chain. It seems entirely unnecessary to me, as one Julia installation can be used conflict-free by many users (it is different than python where it avoids a lot of issues to make many installs). I think that would be possible here too, but I’m not very interested in it personally, it seems like a lot of disk space for no gain.

Can something like this be acceptable as non-first class support?