My impression is the operating system integration required by a modern processor with heterogeneous cores and built-in GPUs is much more complicated than the 486 processors of the 90s. As a result, I don't find it so surprising that the software doesn't appear as well polished upon release of a new processor these days as it used to be.
Although reports of crashes while playing games sounds bad, I'd be much more concerned if Linux were crashing during heavy use, for example, while building version 14.2.0 of the gcc compiler.
Whilst I would guess (!) that your suspicion on the cause is correct, let's not forget that this increase in complexity has also been accompanied by a VAST explosion of the market, and therefore the resources available to prepare launches properly. The Intel that made the 486 was a garage company compared to the Intel that made Arrow Lake.
Either way, as was said in the video: once you lose the trust, it is VERY hard to get it back. I know I won't even consider any Intel hardware that hasn't been out for at least 3, better 6 or 12, months. Especially as this is the second time recently that Intel royally screwed up on stability.
As for Linux: Phoronix had problems with various memory modules. Though I'm not entirely clear on whether the mobo firmware that he had originally used was classified as "release" or not, and updating it resolved the issues.
Linux displayed the EXACT same crashes if you used Proton to run the software on Linux and after the physical damage was done the entire OS would become unstable just like Windows would . Booting into Linux was first reaction when my 13700k started displaying issues before the “secret” was out.
Sorry I meant the ARL issues. The Raptor Lake issues, afaik, are pretty obviously that Intel and its Mobo partners simply pumped too much power into the chips. Which is pretty amazing considering the rather mind-blowing peak power that Raptor Lake-K on desktop is intended to receive.
Either way, even if it did only occur on Windows or (reasonably normal) Linux: I think it's entirely reasonable to expect general purpose desktop/server x86 CPUs to be thoroughly tested in *at least* Windows and Linux. Before shipping. Of course very rare cases may slip through, especially if one has an unusual setup. But these Raptor and Arrow issues don't seem like they're rare. Well, and on the latter Intel didn't even manage to get the PR materials correct, that's certainly OS-independent :D
My impression is the operating system integration required by a modern processor with heterogeneous cores and built-in GPUs is much more complicated than the 486 processors of the 90s. As a result, I don't find it so surprising that the software doesn't appear as well polished upon release of a new processor these days as it used to be.
Although reports of crashes while playing games sounds bad, I'd be much more concerned if Linux were crashing during heavy use, for example, while building version 14.2.0 of the gcc compiler.
Linux crashed On Raptor Lake as well is you used Proton to play those games. It was a straight up Intel problem, not Microsoft or anybody else.
Whilst I would guess (!) that your suspicion on the cause is correct, let's not forget that this increase in complexity has also been accompanied by a VAST explosion of the market, and therefore the resources available to prepare launches properly. The Intel that made the 486 was a garage company compared to the Intel that made Arrow Lake.
Either way, as was said in the video: once you lose the trust, it is VERY hard to get it back. I know I won't even consider any Intel hardware that hasn't been out for at least 3, better 6 or 12, months. Especially as this is the second time recently that Intel royally screwed up on stability.
As for Linux: Phoronix had problems with various memory modules. Though I'm not entirely clear on whether the mobo firmware that he had originally used was classified as "release" or not, and updating it resolved the issues.
Edited: typo
Linux displayed the EXACT same crashes if you used Proton to run the software on Linux and after the physical damage was done the entire OS would become unstable just like Windows would . Booting into Linux was first reaction when my 13700k started displaying issues before the “secret” was out.
Sorry I meant the ARL issues. The Raptor Lake issues, afaik, are pretty obviously that Intel and its Mobo partners simply pumped too much power into the chips. Which is pretty amazing considering the rather mind-blowing peak power that Raptor Lake-K on desktop is intended to receive.
Either way, even if it did only occur on Windows or (reasonably normal) Linux: I think it's entirely reasonable to expect general purpose desktop/server x86 CPUs to be thoroughly tested in *at least* Windows and Linux. Before shipping. Of course very rare cases may slip through, especially if one has an unusual setup. But these Raptor and Arrow issues don't seem like they're rare. Well, and on the latter Intel didn't even manage to get the PR materials correct, that's certainly OS-independent :D
YouTube.com/@usertemir5
@temir5
@temir5org
@tmr7org
@tmrcom8org
@temir5010
discord.com/developer/hlk11
😂😎