4 ms·
> and can't figure out how to do that without looking really bad while staying as Windows 10 Would that really look so bad? Even the Linux kernel dropped 80386
by usrusr 5y ago
> and can't figure out how to do that without looking really bad while staying as Windows 10
Would that really look so bad? Even the Linux kernel dropped 80386 eventually.
Windows 10 feature updates occasionally phasing out hardware support after a few years wouldn't seem wrong at all in my eyes, they could easily explain it as a trade-off necessary for getting "10 forever". And Windows users were already used to not getting their feature update immediately on older hardware, an eventual escalation from late to never wouldn't have been surprising at all.
- TeMPOraL 5y agoBut do you pull kernel updates automatically, unattended? Because Windows feature updates are like that - every now and then they may market them up, including popping up some notification in the system, but otherwise they just get installed automatically over time. If they started dropping compatibility with older CPUs and software with subsequent updates, they could find themselves in the middle of a huge PR mess when one of their automated updates suddenly breaks a chunk of some industry. Makes more sense to create a version boundary if the changes are really as extreme as GP described, preventing large amounts of users from sleep-walking into a disaster.
- usrusr 5y agoWindows 10 feature updates (recently twice a year, named $year'H'$term) have been gated by hardware compatibility lists for quite a while (since the start?), and there's even a distinction between feature update versions that have their own "Long Term Servicing Channel" and those that don't. Sounds familiar? The boundaries you ask for have already been in place, long before 11.
- TeMPOraL 5y agoI didn't know that - especially about "LTSC" for feature updates. Thanks for correcting me.