(andre.arko.net)

333 points steveklabnik | 1 comments | 26 Aug 25 08:15 UTC | HN request time: 0s | source

Show context

rorylawless ◴[26 Aug 25 23:36 UTC] No.45033668[source]▶

Very unfortunate name collision with rv for R (https://github.com/A2-ai/rv).

jxf ◴[26 Aug 25 23:54 UTC] No.45033790[source]▶

Is it really a name collision when they're effectively completely different namespaces? For example, no one thinks Rust's `cargo` might be the same thing as Ruby's obscure `cargo` library.

replies(2): >>45034002 #>>45034878 #

pxc ◴[27 Aug 25 00:25 UTC] No.45034002[source]▶

>>45033790 #

It's not a library. It's an executable that needs to be on the PATH to use it. And the executable has the exact same name.

replies(2): >>45034666 #>>45041823 #

woodruffw ◴[27 Aug 25 02:04 UTC] No.45034666[source]▶

>>45034002 #

At this point, I think the namespace for 2-3 character CLI binaries has probably been clobbered several times over.

replies(1): >>45035494 #

1. pxc ◴[27 Aug 25 04:34 UTC] No.45035494[source]▶

>>45034666 #

My lazy heuristic is to use nix-locate to search through the 100k packages in Nixpkgs, e.g.:

> nix-locate -r 'bin/uv'

Not perfect, but sort of useful for choosing names for executables for internal corporate projects, little wrapper scripts, etc. It's definitely still possible to find reasonable names!

But I've never done the analysis of such short names yet :D

↑

Rv, a new kind of Ruby management tool