• 1 Post
  • 304 Comments
Joined 3 年前
cake
Cake day: 2023年9月12日

help-circle

  • Video game staff has always been treated like shit by the big developers.

    This is another case of the big developers trying to convince their staff that using slop (and, therefore, further devaluing the people) is a good thing.

    If you make a game using “AI,” you’re standing on the shoulders of companies who became giants through theft and lies. They built algorithms, the algorithms stole, and now you’re being told to use those algorithms to benefit the companies who stole to build their databases.

    Yes, it sucks. You’re in a no-win situation. Things will keep getting worse, the way they’ve been getting worse for game development staff for years.

    Folks here will sympathize with your personal plight - unless you use the stolen databases yourself to earn your own livelihood. Because, once you do that, you unfortunately have become part of the problem. Even if you only did it to survive.






  • So, folks who responded are conflating BIOS with UEFI. It’s a common mistake - but they are very different things that serve the same purpose.

    BIOS is older technology. It usually wasn’t risky unless the board was somehow faulty, but there was always some risk because you were directly reflashing the CMOS.

    UEFI is the current technology. If your board is less than 10 years old, you almost definitely have UEFI and not BIOS. It’s stored in NOR flash memory on the motherboard.

    UEFI’s nature and design make it much simpler and safer to update. UEFI can be updated automatically within Linux; BIOS requires the board manufacturer’s utility to reprogram the CMOS.

    I’m simplifying some of this. But this should help explain the conflicting responses of what gets updated under Linux.