What would make a package manager different from any other tool? It's a dependency like any other, it only makes sense to have it locked like any other.
Comments
Log in with your Bluesky account to leave a comment
At a certain point of abstraction/layers in one's stack of tools, choice needs to kick in. For the most part, people get to choose their OS, editor/IDE, and a bunch of other things, even when working on the same project.
The slicing here is of course arbitrary and completely subjective, but I just don't like to be told what package manager to use with a project any more than I like being told what editor to use. To me, they're tools outside the project. They're not run inside the same process as the project code.
This is for local development, of course. One published well-written packages should work regardless of the package manager of the consumers (but Corepack doesn't change anything to that).
Comments