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

help-circle

  • I get it, but we should as a community try to be better than that.

    AI won’t fail. It already is past the point where failing or being a fad was an option. Even if we wanted to go backwards, the steps that were taken to get us to where we are with AI have burned the bridges. We won’t get 2014 quality search engines back. We can’t unshitify the internet.


  • That AI is the one you make or at least host. No one is going to host an online AI for you that is 100% ethical because that isnt profitable and it is very expensive.

    When you vilianize AI you normalize AI use as being bad. The end result is not people stopping use of AI it is people being more okay with using less ethical AI. You can see this with folks driving SUVs and big trucks. They intentionally pick awful choices because the fatigue of being wrong for driving a car makes them just accept that it doesn’t matter.

    It feels dumb, it is dumb, but is what happens.





  • 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.






  • It’s a 100% perfect addition to THE core combat light puzzle platformer games. It also has an age range of 0-99 by both having cute jokes and references that would appeal to older folks while never being even remotely offensive.

    Also yea, what else was there? Closest was make Wukong which primarily crushed the market because it again proved that the new or smaller studios can absolutely give a better AAA experience than the big studios these days by focusing on delivering a game not a storefront







  • The Republican party is policy wise to the right of both National and the NZ First party as a comparison. They will also control all arms of the government and it is potentially possible for them to amend the constitution without any recourse but it isn’t easy.

    So to be clear, they could change our Freedom of Religion and Speech to a Freedom of Christian Religions and “Truthful” Speech and there isn’t a ton that anyone could do to stop them just to give you an idea of the level of power they have taken in this election. It wouldn’t be easy, but the fact that it won’t be impossible should be terrifying.

    The goals they have of criminalizing providing abortion services in all cases for the entire country is entirely possible. They could round up every person in the country of a certain nationality and put them in camps like we did with the Japanese during WW2, Trump already cited this act as being something he is considering to deal with immigration.

    Historically we killed 90% of our indigenous population. When NZ was signing the Treaty of Waitangi, America was executing the Trail of Tears and rounding up 60,000 Native Americans and making them march 100km to live in a desert, a quarter of them died during the move. We’re not even starting in a similar place here and we’re moving far to the right.


  • 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.