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.
AnyOldName3@lemmy.world 2 months ago
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.
DacoTaco@lemmy.world 2 months ago
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
AnyOldName3@lemmy.world 2 months ago
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.