3 ms·
NIH. I have mixed feelings towards NIH people. One bunch is the RIIR crew (ripgrep, ruff, etc.) that produces high quality re-writes with amazing performance a
by datadeft 4y ago
NIH.
I have mixed feelings towards NIH people. One bunch is the RIIR crew (ripgrep, ruff, etc.) that produces high quality re-writes with amazing performance and safety, the other bunch is who re-writing tools without any added value.
I am not sure which category MRSK fall into, there has not been enough details from them to justify this particular re-write.
- burntsushi 4y agoAuthor of ripgrep here. I never saw it as a "rewrite": https://old.reddit.com/r/rust/comments/11updi0/introducing_rewriteitnet_a_collection_of_software/jcppsoi/ https://old.reddit.com/r/rust/comments/11updi0/introducing_r... You might think of it as NIH, but I didn't at the time that I wrote it. Because I saw a gap in the ecosystem that wasn't being filled. grep didn't offer the UX of a tool like ag, and ag didn't degrade gracefully to behave like a grep. (And also wasn't as fast on single file search.) That gap is what motivated me to turn ripgrep from what it was (a test bed for Rust's regex crate) into what it is now. There's a reason why you basically never see me criticizing people about "NIH." Because it's actually quite difficult to accurately cast that criticism. Saying things are NIH is like saying things are broken. It's terribly overused.
- datadeft 4y agoI agree with you. I am not sure what classifies as re-write. For my grep use cases rg is a prefect replacement only it is faster. From this point of view some might say it is a re-write.