3 ms·
“rewrite (the easy parts of) $battle-tested-ancient-coreutil in rust” seems interesting as an exercise or as a way to learn a new language, but i’m not convince
by hprotagonist 5y ago
“rewrite (the easy parts of) $battle-tested-ancient-coreutil in rust” seems interesting as an exercise or as a way to learn a new language, but i’m not convinced of it’s broader utility.
- hexo 5y agohere, the utility could be proof of concept that can be implemented in original tool
- carlmr 5y agoBut then again there's ripgrep, which did just that and is much faster than grep and works perfectly.
- hprotagonist 5y agoi use ripgrep all the time, it's great. i don't think it was ever meant to be "exactly GNU/coreutils grep", and I don't think it ever even tried. The API is totally different, i don't think it's ever been the same, it scratches a similar-but-not-identical itch. https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#posix4ever https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#pos...
- Svetlitski 5y agoI would argue that "the easy parts" of cp account for a very significant fraction of its usage (i.e. copy some files/directories without any other options). The idea with fcp is to make that common use case very fast, not to replace cp and all the options it handles. I definitely can understand the fatigue with "rewrite it in Rust" though, as there is a lot of that. Something you might be interested in is that people have actually gone through the effort of rewriting the actual coreutils to spec in Rust (https://github.com/uutils/coreutils https://github.com/uutils/coreutils).