git-duet VS shell-safe-rm

Have you checked out https://github.com/git-duet/git-duet/ ?

You configure a ~/.git-authors file with people with whom you regularly pair, and use `git duet [author-1] [author-2]` to set primary and secondary commit authors. Env variables set whether you want `Signed-off-by` or `Co-authored-by` trailers.

i ended up using shell-safe-rm plus trash-cli and my own wrapper script around rm that verifies some rules like for example the argument don't start with '/' , if i want to delete for example /home/shin/.local/somefile then the script will not let me and suggest to cd to /home/me/.local and delete from there , same if i do rm /var/somedir.

I use a script called `shell-safe-rm` [1], aliased as `rm` in interactive shells, such that I don't normally use `rm` directly. Instead of directly removing files, they are placed in the trash folder so they can be recovered if they were mistakenly deleted. Highly recommend using a script/program like this to help prevent accidental data loss.

[1] https://github.com/kaelzhang/shell-safe-rm

You could think about using trash-cli or safe-rm if you're too trigger happy with your terminal

So what's really is the difference/advantage compared to at least five other similar utilities already existing (trash-cli, shell-safe-rm, rm-trash, rmtrash, crap)? Can't really be that it uses D as the programming language. As a matter of fact why're there five utilities doing the same thing in the first place?

I meant I'm using safe-rm now but I was using another wrapper when I was younger for who knows why