Hacker News Reader

richdoddon XZ: Repo maintainer Lasse Collin responding on LKML

Posting in support of Collin. I'm sorry this happened to you, and thanks for your hard and thankless work!!

richdoddon Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022

Could you perhaps give an example.

richdoddon Metal shader converter and the missing device-scoped barrier

Hmm OK according to the doucmentation they designed the GPU themselves, so there's no public information on them.

richdoddon Metal shader converter and the missing device-scoped barrier

Does the M1/M2 use ARM designs in the GPU as well as the CPU? If so, it might be possible to work out what could be implemented by looking at the [arm docs](https://developer.arm.com/documentation/102203/0100/Valhall-...).

richdoddon Why Rust?

> There is of course some legitimate worry that the Rust crate ecosystem could devolve into the crazy left-pad world of npm, and it is something to be wary about, but so far the Rust crates keep an overall high quality.

Note that the particular case of left-pad cannot happen with crates.io/cargo, because once published, you cannot unpublish a crate. You can 'yank' it, in which case it will not be resolved by Cargo.toml, but if you put it in Cargo.lock directly (IIUC) it will still work. So we can't have someone pulling a crate and crashing half the ecosystem.

We can however still have lots of other problems that plague all package management systems. Check out `cargo-crev`!!!! It's an awesome idea I'm always plugging to solve the lack of trust in an open library repository. It requires people to participate though.

richdoddon “You meant to install ripgrep”

Can't recommend `cargo crev` enough!!! The more people use it, the more powerful it becomes.

richdoddon “You meant to install ripgrep”

Hi - author of `rg` here :'). I've transferred over to BurntSushi which will give people a bit more assurance that `rg` won't become malware in the future.

I also squatted `memap` and `memap2` for the same reasons.

I wonder if there is an algorithmic way to decide when two crate names are 'near' each other. Then, if you added a crate with `cargo add` and there is another similarly-named crate with much higher usage, a warning could be emitted.

*EDIT* I know there's already https://en.wikipedia.org/wiki/Levenshtein_distance, but I wonder if there is a better measure that looks at e.g. keyboard layouts and likely typos. I'm sure there will have been research done on this.

richdoddon Text layout is a loose hierarchy of segmentation

I agree - I think it will have great value over a long period.