@UncleB wrote:It's just Khoros being Khoros.
😂😂😂isn't that the truth!
Good thing I didn't have a moutful of coffee when I read this......
@coldfusion wrote:
@UncleB wrote:It's just Khoros being Khoros.
😂😂😂isn't that the truth!
Good thing I didn't have a moutful of coffee when I read this......
I read a report that said the more swearing there is in the source code comments, the less buggy the software actually is.
Naturally, after that report came out the corporate overlords patched out anything from the Linux kernel that might be offensive to anyone.
I assume this explains the subsequent decline in code quality.
It's always nice to run into systemd again, and try to figure out after you've upgraded between two distribution releases why telling it, for example, to use zstd and 100% of RAM size for the ZRam device has changed and then the manpages are out of sync because by the time anyone documents systemd it's changed again. They go around shuffling things around so that IBM can be the first to document it and hide it behind a paywall and nobody else will be accurate again for many months.
It's brought entire classes of security issues that had never been possible or even plausible before.
It's only natural that Microsoft hired this clown that wrote it.
In some cases systemd is too lousy even for Microsoft to stomach it. For example, when it goes to compress the system logs ("journal"), it will look at what compressors are available and it will decide randomly what to start using. In WSL, Microsoft patched it to consistently use one algorithm. In practice, every Linux distribution supports at least gzip (DEFLATE) or systemd could have specified "We are using ZStd so make sure you have that." to the distributions, but no. Let's just spin a wheel and use whatever it lands on. No bankruptcy! No bankruptcy! Big million dollars, no bankruptcy!
JWZ accused Richard Stallman of being impossible to work with, but systemd developers are even worse. They have a habit of not responding at all to serious bug and security issues, or responding by flaming the person who reported it so they won't ever come back and report another bug, then closing the bug.
This abuse against bug reporters coming from the systemd people at Microsoft and IBM (mostly) is just this general "don't make us do stuff" mentality, so the only way to get them to fix anything is to dump whatever it is out publicly and shame them into fixing it. (Maybe.) Then they accuse you of being irresponsible.