JuvenalUrbino I like to see tr(1) as the sort of gem which reminds me why sed is evil.
sedevil? Nah... Write-only?--Oh yes!
tr is great because it works with binary files, but, I'm curious to know why you think sed is evil.
pin without sed a whole bunch of pkgsrc packages would be loaded with further patches.
seds (FreeBSD's, Linux's) can be used on binary files too: before @Jay pointed out in a post that NetBSD had a
pkg_alternatives system just like Debian, I used to use
sed -i to "fix" the shebang path in binary compressed python files:
$ sed -i '' -e '1s/env python$/&3.7/' ~/bin/youtube-dl
seddoesn't work with binariy files, so I use
$ ed ~/bin/youtube-dl <<<$'1s/python$/&3.7/\nw\nq\n'
PS. The one thing I find irritating about
sed is the lack of consistency in the handling of the
-i flag everywhere. On FreeBSD, one uses
sed -i '' ... to omit backup file(s). On NetBSD and Linux, it is
sed -i'' ...--ie. without the intervening space.