[–] 11 points 2 months ago* (2 children)

Paraphrasing a tidbit of information from Northwest Repair, who's a guy on YouTube that does board-level repairs on computer hardware:

Apparently, reprogramming the firmware config and changing the RGB light status on a DRAM module are both done through the same SPI bus. Consequently, every time you change the RGB lighting, it has a tiny chance of accidentally bricking the stick.

So not only is RGB an additional upfront cost that consumers might not want, it could even contribute to long-term costs by reducing the lifetime of some components.

  • source
  • parent
  • context
  • [–] 36 points 3 months ago*

    Personal ownership was so pre-2020s anyways.

    I can spend $800 on something I can use for years and resell, gift, or repurpose. Or, I can instead spend $180 annually under the threat of my data being destroyed if I stop giving into the extortion. Easy choice, really. /s

  • source
  • [–] 8 points 3 months ago* (11 children)

    Native CPU instruction execution doesn't guarantee 1:1 throughput, let alone account for the fact that the PS5 has over double the raw power of a Steam Deck.

    Translating API calls from the guest software to the host's equivalent isn't free, either. If the emulator uses hardware virtualization, you can also add the extra cycles spent every time the guest needs to perform a hypervisor call.

    In a decade, maybe the IPC gains would be enough for something with fewer cores and lesser clock speeds to be able to do the equivalent work of a PS5. Right now? With a Steam Deck? Good luck running anything more intensive than an indie title at full speed.

  • source
  • parent
  • context
  • [–] 6 points 3 months ago (1 child)

    No. It's accurate. They're the kind of people who think of themselves as temporarily embarrassed millionaires, and they'll be damned if their hard-earned future money goes to the poor when they finally strike it rich.

  • source
  • parent
  • context
  • view more: next ›