←back to thread

365 points tanelpoder | 1 comments | | HN request time: 0.203s | source
Show context
Calavar ◴[] No.44977988[source]
Why does a package manager need a formatter at all?
replies(1): >>44978009 #
kristjansson ◴[] No.44978009[source]
Is cargo just a package manager? Go?
replies(5): >>44978076 #>>44978124 #>>44978190 #>>44979308 #>>44980986 #
Calavar ◴[] No.44978124[source]
Cargo is a hybrid of package manager and build system. So it has frontend fommands wrapping a formatter and loads of other stuff, like code linters, as part of the build system. I've used cargo to build projects even when they have no dependencies and I don't plan to bundle them up and publish them as crates.

I don't know much about go.

replies(1): >>44978254 #
Hamuko ◴[] No.44978254[source]
uv is also a package manager and a build system.

https://docs.astral.sh/uv/concepts/build-backend/

replies(2): >>44981002 #>>44984034 #
1. RossBencina ◴[] No.44981002[source]
Thanks for pointing that out. This is news to me. uv has been on my radar for a while and was considering switching to it as a better dependency manager. I didn't realise that it had ambitions beyond being "a better pip." At face value this is a real turn-off. Definitely violates the "do one thing and do it well" principle and puts it squarely in the "does complicated things that I want to avoid" (like poetry) category.