'Why not add a base16 into coreutils?
Both base32 and base64 CLI utils are part of gnu coreutils. So, why not add a base16?
Solution 1:[1]
GNU coreutils is free. It's people very, very hard work they are doing for free. You are using it completely for free. How much have you donated? Donate them. Pay them if you want something.
Why not add a base16 into coreutils?
It costs work, both implementing, but mostly the never ending maintenance. If something is not needed, it's better not to add it and reduce the work and concentrate on what's important. Maintaining current commands, so they are up-to-date with all systems and be consistent and work, is way more important. Some even say, that (especially in open-source) a project leader has most importantly decide what features to reject, not which to add.
So, how much will you pay for implementing and then endless maintaining a base16 utility in GNU coreutils?
Solution 2:[2]
In my opinion, this is due to the fact that hex encoding doubles the amount of data being encoded. This approach was deemed inappropriate.
P.S. Here is a C# example of the console tool that provides base16 encoding. Application input can be obtained from files, command line, keyboard or by redirecting output from another console application according to so called "Unix way" software. Unfortunately, it uses the Windows API but can be redesigned for Linux.
Sources
This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.
Source: Stack Overflow
| Solution | Source |
|---|---|
| Solution 1 | KamilCuk |
| Solution 2 | ng256 |