>>51The state of the field is shit because people keep stepping back and reinventing wheels, instead of solving new problems.
The state of the field is shit because people don't even recognize problems with the field, but muddle through all the shit required due to inertia. Like the fact that source code is still fucking text files, instead of having semantic editors, or the incompatible application boundaries when you want to process data using functionality found in multiple programs. (and serialization to arbitrary text and/or bytes in the Unix way is a bullshit red herring that makes more problems than it solves)
The state of our field is shit because people focus on bytes & cycles when it's completely unnecessary, or limiting problem scopes to make things less difficult, to stroke their own cock via "programming" instead of getting real work done.
The state of our field is shit because OSes are still fundamentally based on C APIs, meaning that taint of brittleness will always be there.
Everything suckless says, does & stands for is right in the middle of the shittiest shit in the field.