3 ms·
The entire thread is about how the benefit of these tools are not worth the hassle of copying the binaries around because everyone can't just install or modify
by unsnap_biceps 2y ago
The entire thread is about how the benefit of these tools are not worth the hassle of copying the binaries around because everyone can't just install or modify the servers.
You keep modifying the argument for some sort of moral win I guess, devolving into name calling when people just don't agree with your position. Very professional of you.
Regardless, I presume you're just having a bad day. I hope it goes better for you and you can find some peace and calm down.
- burntsushi 2y agoThe original comment said nothing about modifying servers or AWS engineers installing random shit. That was you. I responded to "moving binaries around," and you started yapping about change management. Two totally different things. Like obviously if you have a locked down environment, then only install what you need. But this is not what the original poster was referring to specifically. ripgrep even specifically calls out this exact use case right in its README: https://github.com/BurntSushi/ripgrep/?tab=readme-ov-file#why-shouldnt-i-use-ripgrep https://github.com/BurntSushi/ripgrep/?tab=readme-ov-file#wh... > You need a portable and ubiquitous tool. While ripgrep works on Windows, macOS and Linux, it is not ubiquitous and it does not conform to any standard such as POSIX. The best tool for this job is good old grep. So, you presume too much friendo. Now, go away.