Hacker News Reader

Comment by benatkin | Hacker News Reader

Looks like the GUI library's crate came out first:

https://crates.io/crates/iced/versions https://crates.io/crates/iced-x86/versions

I'm not sure there's a naming conflict here. There is little overlap between x86 decoding and a GUI library. If software is eating the world, then it's similar to Giant Bicycles and Giant Food Stores.

View on HN

I didn't mean to imply priority: a clash is just a clash, not a sign that either project isn't entitled to the name. It's just an unfortunate namespace problem: language package managers (overwhelmingly) flatten things into a single-level namespace, and so we end up with things like this.

> There is little overlap between x86 decoding and a GUI library.

I work on a graphical tool that visualizes x86 binaries! It uses iced (the decoder), and it could very easily end up using iced (the GUI library).

But then you'd be obliged to call it Ice Cubed

icequare

The main thing I disagree with you on, is that there is a namespace collision because of the package manager, or that there is a namespace collision because both use Rust. If there is a namespace collision, it should be because they're both tools used by developers. The package manager issue is solved easily by adding something to the package name. As for the language, Rust is shaping up to be more like C++ than Ruby or Python, where the main community is more about the language and the standard library and less about the myriad different uses of it.

I think both can keep their names long-term.

Reply on news.ycombinator.com