@Mr_NutterButter@matrix "cksum is a shell command for generating a checksum " https://en.wikipedia.org/wiki/Cksum With today's hardware cksum is infinitely fast, if your new software is slower than GNU's implementation then your code has a problem. Why ? Because GNU has the history/spaghetti baggage of itself, that's how all software ends up over time in every case. The only way to mitigate that is via making small pieces of spaghetti code you can delete/re write fast.
Performance and code design aside, you also need: -Stability -Compatibility -Legal protection The rust version doesn't currently fill these, and it won't ever fill the last one "legal protection" because of it's permissive licensing which screams EEE. https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish
@Mr_NutterButter@matrix The unportable and absolutely proprietary language implementation turned out to be 17x slower at calculating checksums than code designed to prioritize portability over speed.
"cksum is a shell command for generating a checksum "
https://en.wikipedia.org/wiki/Cksum
With today's hardware cksum is infinitely fast, if your new software is slower than GNU's implementation then your code has a problem.
Why ? Because GNU has the history/spaghetti baggage of itself, that's how all software ends up over time in every case. The only way to mitigate that is via making small pieces of spaghetti code you can delete/re write fast.
Performance and code design aside, you also need:
-Stability
-Compatibility
-Legal protection
The rust version doesn't currently fill these, and it won't ever fill the last one "legal protection" because of it's permissive licensing which screams EEE.
https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish