24
submitted 2 weeks ago by floofloof@lemmy.ca to c/technology@beehaw.org
top 7 comments
sorted by: hot top controversial new old
[-] Artyom@lemm.ee 31 points 2 weeks ago* (last edited 2 weeks ago)

Future chips not affected by THIS cpu bug.

[-] remotelove@lemmy.ca 8 points 2 weeks ago

Future chips not affected by THIS cpu bug yet.

[-] Gormadt@lemmy.blahaj.zone 14 points 2 weeks ago
[-] Quexotic@beehaw.org 4 points 2 weeks ago

I've got one of those laptop chips and I feel exactly the same. I'm going to be watching my temps very closely. My trust is absolutely gone

[-] ulkesh@beehaw.org 9 points 2 weeks ago* (last edited 2 weeks ago)

The damage is done, though. And the fact that Intel wouldn’t do anything about damaged CPUs (edit: without requiring the customer to call over and over and over about the RMA) or recall affected CPUs is quite telling. So I’m jumping ship to AMD for my next build.

[-] floofloof@lemmy.ca 4 points 2 weeks ago* (last edited 2 weeks ago)

You and everyone else. I'd have to see a few problem-free years from Intel before I'd return to them.

[-] Dark_Dragon@lemmy.dbzer0.com 5 points 2 weeks ago

What about the current chip "paid" and "bought" by the customers?

this post was submitted on 31 Aug 2024
24 points (100.0% liked)

Technology

37574 readers
169 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS