For context, Meta reported 40 billion in revenue during that period, with 24Bn in expenses and made 13bn for the period. All those numbers are up from the same period last year.
So I'm gonna go with "probably, yeah".
MudMan
joined 6 months ago
Is the fuel in this case a bunch of damaged 13 and 14th gen CPUs?
Oh, gotcha. Yeah, direct phone-to-phone transfers have been rare and mostly replaced by cloud shares for me. It's just easier to add the file in question to some cloud destination that allows link sharing instead.
To share from where to where? For sharing with your own computer at home I just have a SMB share and I use Cx File Explorer to access it like I would on a PC. For direct phone to phone sharing... I haven't had to do that in ages, so I wouldn't know. I have a number of solutions for cloud file sharing that are platform agnostic, though.
Oh, I absolutely could have. It would lose a couple of cores, but the 13th gen is pretty linear, it would have performed more or less the same.
Thing is, I couldn't have known that then, could I? Chip reviews aren't aiming at normalizing for temps, everybody is reviewing for moar pahwah. So is there a way for me to know that gimping this chip to run silently basically gets me a slightly overclocked 13600K? Not really. Do I know, even at this point, that getting a 13600K wouldn't deliver the same performance but require my fans to be back to sounding noticeable? I don't know that.
Because the actual performance of these is not to a reliable spec other than "run flat out and see how much heat your thermal solution can soak" there is no good way to evaluate these for applications that aren't just that without buying them and checking. Maybe I could have saved a hundred bucks. Maybe not. Who knows?
This is less of a problem if you buy laptops, but for casual DIY I frankly find the current status quo absurd.
Whoa, that's even worse. It's not just the uncertainty of knowing whether Intel will replace your hardware or the cost of jumping ship next time. Intel straight up owes you money. That sucks.
You're not wrong, but "we've been winging it for decades" is not necessarily a good defense here.
That said, I do think they did look at their performance numbers and made a conscious choice to lean into feeding these more power and running them hotter, though. Whether the impact would be lower with more conservative power specs is debatable, but as you say there are other reasons why trying to fake generational leaps by making CPUs capable of fusing helium is not a great idea.
"Clearly damaged" is an interesting problem. The CPU would crash 100% of the time on the default settings for the motherboard, but if you remember, they issued a patch already.
I patched. And guess what, with the new Intel Defaults it doesn't crash anymore. But it suddenly runs very hot instead. Like, weird hot. On a liquid cooling system it's thermal throttling when before it wouldn't come even close. Won't crash, though.
So is it human error? Did I incorrectly mount my cooling? I'd say probably not, considering it ran cool enough pre-patch until it became unstable and it runs cool enough now with a manual downclock. But is that enough for Intel to issue a replacement if the system isn't unstable? More importantly, do I want to have that fight with them now or to wait and see if their upcoming patch, which allegedly will fix whatever incorrect voltage requests the CPU is making, fixes the overheating issue? Because I work on this thing, I can't just chuck it in a box, send it to Intel and wait. I need to be up and running immediately.
So yeah, it sucks either way, but it would suck a lot less if Intel was willing to flag a range of CPUs as being eligible for a recall.
As I see it right now, the order of operations is to wait for the upcoming patch, retest the default settings after the patch and if the behavior seems incorrect contact Intel for a replacement. I just wish they would make it clearer what that process is going to be and who is eligible for one.
No, I have a DDR5 setup. Which is why my motherboard was way more expensive than 100 bucks.
The problem isn't upgrading to a entry level AM5 motherboard, the problem is that to get back to where I am with my rather expensive Intel motherboard I have to spend a lot more than that. Moving to AMD doesn't mean I want to downgrade.
I mean, happy for you, but in the real world a 200 extra dollars for a 400 dollar part is a huge price spike.
Never mind that, be happy for me, I actually went for a higher spec than that when I got this PC because I figured I'd get at least one CPU upgrade out of this motherboard, since it was early days of DDR5 and it seemed like I'd be able to both buy faster RAM and a faster CPU to keep my device up to date. So yeah, it was more expensive than that.
And hey, caveat emptor, futureproofing is a risky, expensive game on PCs. I was ready for a new technology to make me upgrade anyway, if we suddenly figured out endless storage or instant RAM or whatever. Doesn't mean it isn't crappy to suddenly make upgrading my CPU almost twice as expensive because Intel sucks at their one job.
The article is... not wrong, but oversimplifying. There seem to be multiple faults at play here, some would continue to degrade, others would prevent you from recovering some performance threshold, but may be prevented from further damage, others may be solved. Yes, degradation of the chip may be irreversible, if it's due to the oxidation problem or due to the incorrect voltages having cuased damage, but presumably in some cases the chip would continue to work stable and not degenerate further with the microcode fixes.
But yes, agreed, the situation sucks and Intel should be out there disclosing a range of affected chips by at least the confirmed physical defect and allowing a streamlined recall of affected devices, not saying "start an RMA process and we'll look into it".
"Jello" is a brand name, which I think may be the example most people in the US specifically don't realize. There are tons of others.
I think "googling" counts because a) it kinda makes sense even without the branding, b) I hear it all the time, and c) I say it myself even though I haven't used Google as my default search engine for ages.