Nobody was complaining about the Switch CPU. It was a pretty solid choice for the time. It outperformed the Xbox 360 somewhat, which is really all it needed to do to support last-gen ports. Like I said, the big annoyance that was specifically CPU-related from a dev perspective was the low thread count, which made cramming previous-gen multithreaded stuff into a fraction of the threads a bit of a mess.
The point of a console CPU is to run games, it’s not raw compute. The Switch had what it needed for the scope of games it was running. On a handheld you also want it to be power efficient, which it was. In fact, the Switch didn’t overclock the CPU on docked, just the GPU. Because it didn’t need it. And we now know it did have some headroom to run faster, jailbroken Switches can be reliably clocked up a fair amount. Nintendo locked it that low because they found it was the right balance of power consumption and speed to support the rest of the components.
Memory bandwidth ended up being much more of a bottleneck on it. For a lot of the games you wanted to make on a Switch the CPU was not the limit you were bumping into. The memory and the GPU were more likely to be slowing you down before CPU cycles did.
The Switch CPU performs extremely poorly as far as gaming is concerned. Case in point, you cited Cities: Skylines, a quick web search suggests performance is terrible on the Switch and it seems to have been abandoned shortly after release.
While I don’t doubt the Switch 2 CPU will be sufficient for games released by Nintendo, from a broader gaming perspective (gaming is not only Nintendo), it is likely the Switch 2 CPU will also be subpar and will perform worse than the Steam Deck (which is a handheld and its CPU is also subject to efficiency requirements). Whether Nintendo users know/care/don’t care about this is irrelevant. We are talking about objective facts.
What is “par” here?
Nobody was complaining about the Switch CPU. It was a pretty solid choice for the time. It outperformed the Xbox 360 somewhat, which is really all it needed to do to support last-gen ports. Like I said, the big annoyance that was specifically CPU-related from a dev perspective was the low thread count, which made cramming previous-gen multithreaded stuff into a fraction of the threads a bit of a mess.
The point of a console CPU is to run games, it’s not raw compute. The Switch had what it needed for the scope of games it was running. On a handheld you also want it to be power efficient, which it was. In fact, the Switch didn’t overclock the CPU on docked, just the GPU. Because it didn’t need it. And we now know it did have some headroom to run faster, jailbroken Switches can be reliably clocked up a fair amount. Nintendo locked it that low because they found it was the right balance of power consumption and speed to support the rest of the components.
Memory bandwidth ended up being much more of a bottleneck on it. For a lot of the games you wanted to make on a Switch the CPU was not the limit you were bumping into. The memory and the GPU were more likely to be slowing you down before CPU cycles did.
The Switch CPU performs extremely poorly as far as gaming is concerned. Case in point, you cited Cities: Skylines, a quick web search suggests performance is terrible on the Switch and it seems to have been abandoned shortly after release.
While I don’t doubt the Switch 2 CPU will be sufficient for games released by Nintendo, from a broader gaming perspective (gaming is not only Nintendo), it is likely the Switch 2 CPU will also be subpar and will perform worse than the Steam Deck (which is a handheld and its CPU is also subject to efficiency requirements). Whether Nintendo users know/care/don’t care about this is irrelevant. We are talking about objective facts.
I swear, every time into one of these the Dunning-Kruger gets me.
I know it’s coming, but it gets me anyway.
Keep telling yourself that!
You don’t know anything about the Switch 2’s CPU and you just assumed it will be better because “trust me bro”.
And you have the gall to call other people stupid (note that I never insulted you) and in such passive-aggressive way too.