Re:Wolfsort: An ultra-fast hybrid radix sort algorithm
by bane on Saturday July 25, 2020 @09:27AM
(#23949016)
C has an interesting culture of terse variable and function names, and limited comments. It comes from an entirely different mindset and time period in software. It predates most "modern" concepts of software re-usability that eventually turned into enterprise OOP practices and was crystalized in Java and C#.
It's not great anymore. The software world has moved on to understanding how important these things are (and even often takes things too far), but C seems a bit stuck in its ways.
Re:Wolfsort: An ultra-fast hybrid radix sort algorithm
by vii on Saturday July 25, 2020 @11:11AM
(#23949747)
The value of comments and references depends on the software context. If inexperienced people are expected to be editing or reading the code they're more valuable. However, they are expensive to keep in sync with changes to the implementation and the value has to balanced against this cost.
Java and C# did not replace C. They're typically used for different tasks.
Objectively speaking, do we have evidence these enterprise OOP practices lead to better software?
Re:Wolfsort: An ultra-fast hybrid radix sort algorithm
by croutonix on Saturday July 25, 2020 @07:36AM
(#23948435)
Comments increase compile time!
Re:Wolfsort: An ultra-fast hybrid radix sort algorithm
by scaredginger on Saturday July 25, 2020 @07:41AM
(#23948457)
Not to mention file sizes!
This repo contains a few thousand lines of code without so much as a single comment. In my experience that tends to happen much less in other languages. And it's not like this C code is obvious.