Quotes of the week
The LinuxReviews Quote of the week is some free software related quote which is shown on the front page of this website. What quote is used is typically random and everything goes as long as it's somehow related to free software or computers or anything else remotely relevant. The same quote will sometimes stay up one week, sometimes four. The quotes have so far been thrown away when they have been replaced. That may be a waste so this page was created to collect them when they are thrown away.
Week 40, 2019
"The purpose of a non-free program is to subjugate people. And typically that leads to malicious functionalities. Many of the most widely non-free programs are MALWARE. Now, note that malware is totally different issue, a different consent. The difference between free software and proprietary software is a matter of how the program is distributed to users, on what conditions for instance it's distributed. And the same code, any code, could be distributed as free software, any code could be distributed as proprietary software. Sometimes the same code is distributed both ways in parallel. It's a matter of how the code is distributed. It is not a technical issue, it is not a technical distinction between free and proprietary. Technical distinctions are things like what features does the program have, how does it work, how was the code written? Those are all technical things. This is a social, ethical and political distinction which is why it is so important."
Week 41, 2019
"No System Is Safe!"
Week 45, 2019
"Please do not stick defines into a function body. That's horrible."
Week 46, 2019
"These processors are buggy as hell, and some of these bugs don't just cause development/debugging problems, but will *ASSUREDLY* be exploitable from userland code."
Week 49, 2019
"I can't help but point out that if we do this, then we're forcing everyone to pay a price in terms of runtime performance and codesize -- even if they're on a processor where this doesn't matter."
Week 50, 2019
"Quite frankly, this is f*cking moronic. The whole thing seems to be designed around stupid interfaces, for completely moronic reasons. Why should we do this?"
Week 51, 2019
"Yes, doing it in the kernel is "more robust". But don't play games, and stop the lying. It's more robust because we have maintainers that care, and because we know that regressions are not something we can play fast and loose with. If something breaks, and we don't know what the right fix for that breakage is, we *revert* the thing that broke."
Week 52, 2019
"I have zero confidence that we understand the real problem, but we do need to do something with this."
Week 1, 2020
"So the code in question is pure garbage. You can't do spinlocks like that. Or rather, you very much can do them like that, and when you do that you are measuring random latencies and getting nonsensical values, because what you are measuring is "I have a lot of busywork, where all the processes are CPU-bound, and I'm measuring random points of how long the scheduler kept the process in place".
And then you write a blog-post blamings others, not understanding that it's your incorrect code that is garbage, and is giving random garbage values."
Week 4, 2020
"this: (..) is just complete gibberish. And I have no idea what problem you're trying to solve how. (..) So what you're doing is, mark the CPU 'idle' when the MPERF/TSC ratio < 1%, and then frob the vruntime such that it will hopefully preempt. That's pretty disgusting."
Week 5, 2020
"You're weasel-wording, and making up arguments that aren't valid."