Sure, but if tomorrow uv and ruff ceased to exist, we could all go back to any number of other solutions.
Maybe you could. I would stare longingly into the void, wondering if I can ever work another python project after having experienced uv, ruff, and ty.
Such an outcome would make me wonder regarding the wisdom of "It is better to have love and lost than to have never loved at all."
While I hope it never comes to that, all the code is MIT licensed, I would assume everyone would make the sensible decision for fork it.
I see Apache and MIT license files in their GitHub. What's to prevent the community from forking and continuing development if the licenses change?
Personally I would stop using Python again. uv is the one thing that made it bearable.
I would just ditch Python, like I did 8 years ago.
>Sure, but if tomorrow uv and ruff ceased to exist, we could all go back to any number of other solutions.
Or, more relevant to this conversion: If they closed source tomorrow, the community could fork the current version.
I dont wanna go back to micromamba, pixi is my happy place (which builds on uv).
UV is so much nicer than the other options.
Eurgh, I do not want to ever touch Poetry or pyenv again, thank you very much.
I wish that were also true for the case of Claude/Codex/etc
…if tomorrow python ceased to exist, we could all go back to any number of other solutions.
I mean, if you believe the hype on this website, Claude Code could build a perfect clone of uv in a few hours using only the documentation.
Ruff is nice, but not important, uv is one of the few things making the python ecosystem bearable. Python is a language for monkeys, and if you don't give monkeys good tools, they will forever entangle themselves and you. It is all garbage wrapped in garbage. At least let me deploy it without having to manually detangle all that garbage by version.
I'm done pretending this is a "right tools for the right job" kind of thing, there's wrong people in the right job, and they only know python. If no one self-writes code anymore anyway, at least use a language that isn't a clusterfuck of bad design decisions, and has 1 trillion lines of code in the collective memory of people who don't know what a stack is.