3 ms·
> The outrage that they release a new major version that requires new hardware is…weird. My impression is that the outrage is because the requirement is... wei
by vladvasiliu 5y ago
> The outrage that they release a new major version that requires new hardware is…weird.
My impression is that the outrage is because the requirement is... weird. As in artificial. It will support new, lower-end CPUs, but not older, more powerful CPUs.
I seem to remember the cutoff was 8th gen Intels. A friend has an XPS with a 7th gen i7H. That thing is much more powerful than the dinky i5u I have in my work laptop, but since mine is 8th gen it will be able to run Win 11, but not his. My desktop has an overclocked 3rd gen i7 that runs circles around both of the laptops combined. Can't run win11 either.
I get there's the TPM thing, although it's not clear to me why it's so important or whether it's not at all possible (as opposed to just uncommon) to have a TPM v2 on an older than 8th gen CPU.
- jmkni 5y agoI'm wondering if this will allow them to get rid of loads of legacy code in the Windows codebase over time? If not, then I really don't get it.
- vladvasiliu 5y agoI wouldn't hold my breath. I'm not a Windows user, but my understanding is that the legacy code allows people to run old software, so I wouldn't expect this to go away just because the required minimum CPU is fairly new. If anything, it should stay in place, as an argument to push adoption of Windows 11: "yeah, you need brand-new computers, but don't worry, all your old software will still work as before".
- josefx 5y ago> but my understanding is that the legacy code allows people to run old software There might be hardware support that can be cut, if specific x64 features are guaranteed to exist on the newer generation or bugs are known to be fixed you can drop the fallback code without breaking anything.