• 0 Posts
  • 22 Comments
Joined 1 year ago
cake
Cake day: April 21st, 2024

help-circle



  • Linus shouldn’t have to get involved at all. Each part of the Kernel should be handled independently by the maintainers. Linus responding publicly to outside forces is fine but once he has to step in to handle public fights between individuals who are supposed to work together it is a problem.

    Linux staying C focused is a valid thing to do. It is very hard to get folks to contribute to the kernel and if you cut out anyone who doesn’t know Rust, a language with at best 5% the adoption rate of C, you will run into spots where sections of the kernel are unmaintained due to no willing and qualified person covering it.

    Adding Rust based functionality and support is great. Changing APIs to require maintainers to learn Rust to continue to maintain the code they are experts in is unacceptable.


  • You approved of it being okay to make up negative things about a person simply because they are a billionaire. You’re saying, why fact check this meme, dude is rich so I agree with their nonsense regardless.

    It is always okay to punch up, but it is silly and foolish to punch up randomly. It is a major part of mob mentality and why we are in the position we are today. It shouldn’t be a surprise that billionaires use social media wharrgarbl to fight other billionaires. We literally just saw one use this tactic to influence a major election.




  • I get it, and I agree that most people are not in the right job. This is a big part of why folks want things like a higher minimum wage and socialized healthcare. People often are stuck in jobs because they NEED something from that job and are unable to look around. Then on the other side, sometimes folks find their calling but it pays $9 an hour and they feel a need to try to do better.

    I work with a lot of folks for example that got into management because they think that is what you do. They hate the job, they miss writing code, they are awful managers. It’s a very backwards way of living your life.

    I am just trying to talk to an ideal and real scenario here. The idea that all jobs suck and that is life is exactly what keeps people down. That is the lie folks believe that keeps them from seeking peace and contentment. We gotta fight that even if we also know that it isn’t easy to find a spot and when you do it might not be viable with the rest of your life.





  • He was elected as Dictator many times on a yearly basis and sometimes multiple times a year. He was so vastly popular the citizenry they killed the assassin’s, hunted down an heir and put him in power.

    Julius Ceasar and his follow on Agustus were insanely capable leaders that did great things for their country. The empire was so great and lasted twice the time America has, it’s fall caused the Dark Ages.

    Rome is a bad example here because technically the Dictatorship was good for them. Rome fell due to corruption that came in via enabling the Christian church to operate freely. Now that is a much better analog here that we enabled religious organizations to become tax free political action committees and uncapped their ability to influence government. This meant the evangelical grifters became the most powerful political entities in America.





  • This is a patch from the hardware vendor so I am assuming that the ask is not that the hardware vendor take responsibility but that they not release buggy hardware. That is what I mean about the validation issue.

    The attack vector is shared in the patch so it isn’t entirely a theory.

    There is a comment from Linus about how this patch is only needed for some hardware and doesn’t apply to others but I don’t get his relevance there as different hardware validates against different use cases and their source logic might be entirely disparate.

    So my validation talk is simply saying that bugs happen. My concern here is what more should a hardware vendor do beyond submitting a kernel patch? You can’t just not have the bug, and if you recall the part someone else will just keep theirs in the field and take all the market share and roll the dice that their bugs don’t get exploited.


  • Is this really the hardware vendor’s problem though? It’s the consumers problem.

    I bring up full validation because the concern here is putting in a speculative fix. If the ask is, why was the hardware like that in the first place the answer is because it can’t be fully validated. If the ask is why should a speculative fix go into the Kernel it is because the consumers are not on top of tree and if a fix has a chance of never being exploited it needs to be pulled in years ahead so it goes into an LTR that customers migrate to BEFORE the issue comes up.


  • Fully validating hardware is an insane task that hasn’t been really done in years. It would mean 5 years between chip releases and a 2-5X in cost to produce, and people wouldn’t follow the validated configs anyways. If we followed the validated hardware spec we would have 50 min boot times and not go past a 3.5Ghz clock.

    People have the choice today on if they want to run on validated hardware. You can opt in to get a 2.8Ghz part that supports 2666MT/s that is mostly tested and validated, or you can get a 5Ghz part that supports 6000MT/s that is only partially validated. They cost the same price. What do folks think people pick?