I’d say it’s actually a better market signal rather than indications of huge problems. “See, our competitiors send out defective products; we are holding back to make sure ours ship correctly.”
That’s exactly what enterprise/datacenter customers want to hear: a dedication to stability.
Any large scale manufacturer like AMD knows about what % of defective returns they get. They’re using the heat on Intel to help make their numbers look better.
Actually, I think it’s not about defect numbers. This is about delaying until Intel releases the microcode update. They want to be compared after the (potentially) performance tanking update from Intel. Which is hilarious because Intel gave a date after AMD’s initial launch date.
I think it’s also fair as a lot of reviewers aren’t going to bother retesting after Intel releases updates and comparing with AMD after the 9000 series hype has died down, if they had just recently did so for the AMD launch.
… You just contradicted yourself there with the timeline/dates lol.
Wait for intel patch, but release date of cpus is before the expected release date of the microcode patch.
You’ve misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they’d be delaying the release date, and that new release date is after the microcode update.
Ah, you meant original release date of the amd cpus.
Ye, makes sense.
I personally think they wanted to verify to have no issues in their cpu’s because intel is kinda euh… In a very bad state atm haha. You dont want to be part of that right now xD
It wasn’t me who you replied to originally - I agree that it’s most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they’ve had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.
I think you mean Occam’s Razor. AMD signaling responsibility is a simpler explanation as a “dunk” on Intel, them having a similar issue as Intel seems far too coincidental. They’re on completely different nodes, so there’s no reason their issues would be related.
So my take is that AMD thinks Intel’s fix is going to degrade performance significantly, so they want to wait to ensure their launch is as impactful as possible (bigger perf delta, more time to find hardware issues, etc). If AMD can show strength and reliability while Intel suffers, they could snap up much more market share (and improve product availability at launch).
Intel announces two generations of defective processors and AMD gives up that opportunity to recall their own launch? Must be something very wrong with the batch.
I’d say it’s actually a better market signal rather than indications of huge problems. “See, our competitiors send out defective products; we are holding back to make sure ours ship correctly.”
That’s exactly what enterprise/datacenter customers want to hear: a dedication to stability.
Nah something fishy
Any large scale manufacturer like AMD knows about what % of defective returns they get. They’re using the heat on Intel to help make their numbers look better.
Actually, I think it’s not about defect numbers. This is about delaying until Intel releases the microcode update. They want to be compared after the (potentially) performance tanking update from Intel. Which is hilarious because Intel gave a date after AMD’s initial launch date.
I think it’s also fair as a lot of reviewers aren’t going to bother retesting after Intel releases updates and comparing with AMD after the 9000 series hype has died down, if they had just recently did so for the AMD launch.
… You just contradicted yourself there with the timeline/dates lol.
Wait for intel patch, but release date of cpus is before the expected release date of the microcode patch.
You’ve misunderstood. The original release date was set, then Intel announced the microcode update, which was after the original release date, then AMD announced that they’d be delaying the release date, and that new release date is after the microcode update.
Ah, you meant original release date of the amd cpus.
Ye, makes sense.
I personally think they wanted to verify to have no issues in their cpu’s because intel is kinda euh… In a very bad state atm haha. You dont want to be part of that right now xD
It wasn’t me who you replied to originally - I agree that it’s most likely AMD are just being super cautious given historically how many times bad news for their competitors has been falsely equated by the press as equivalent to a minor issue they’ve had, and the delay moving things after the microcode update and therefore making launch-day benchmarking more favourable is just a bonus.
Hanlon’s razor, don’t overthink it. No need for mindless conspiracy theories based on zero data. If it’s aajor concern we’ll hear something no doubt.
I think you mean Occam’s Razor. AMD signaling responsibility is a simpler explanation as a “dunk” on Intel, them having a similar issue as Intel seems far too coincidental. They’re on completely different nodes, so there’s no reason their issues would be related.
So my take is that AMD thinks Intel’s fix is going to degrade performance significantly, so they want to wait to ensure their launch is as impactful as possible (bigger perf delta, more time to find hardware issues, etc). If AMD can show strength and reliability while Intel suffers, they could snap up much more market share (and improve product availability at launch).
no u
Coincidences are real my guy.