←back to thread

365 points tanelpoder | 3 comments | | HN request time: 0.654s | source
Show context
alkh ◴[] No.44978054[source]
I enjoy using uv a lot but am getting afraid that it is getting bloated for no reason. For ex., the number of niche flags that a lot of subcommands support is very high + some of them seemingly achieve the same result(uv run --no-project and uv run --active). I'd rather them working on improving existing tools and documentation than adding new (redundant) functionality
replies(4): >>44978481 #>>44978543 #>>44981333 #>>44986265 #
treyd ◴[] No.44978481[source]
Are they baked into the main executable or are they separate binaries (a la apt, cargo, etc)?
replies(1): >>44978599 #
1. charliermarsh ◴[] No.44978599[source]
It's a separate binary -- we install Ruff if you invoke `uv format`. So if you don't invoke `uv format`, there's no impact on the binary size, etc.
replies(1): >>44984283 #
2. HelloNurse ◴[] No.44984283[source]
But, for example, my project already uses Ruff, and I have to worry about having a "managed" extra copy of Ruff that subtly alters the normal functioning both of "uv tool run" and of ruff itself.
replies(1): >>44987412 #
3. zanie ◴[] No.44987412[source]
It's intentionally distinct from the `uv tool` interface — it won't change `ruff` or `uv tool run` behaviors.