Re:Anomalous CPU utilization on Windows build node caused by...
by longcommonname on Friday July 12, 2019 @01:29PM
(#20422488)
How long do you think a major OS should have 32 bit support? Everything cant be supported forever.
[ Parent
| on HN ]
Re:Anomalous CPU utilization on Windows build node caused by...
by AnIdiotOnTheNet on Friday July 12, 2019 @01:31PM
(#20422517)
Why not? We live in a world where the latest processor from Intel still boots into 16 bit real mode, and we have emulators and virtual machines.
Re:Anomalous CPU utilization on Windows build node caused by...
by ryanianian on Friday July 12, 2019 @01:34PM
(#20422538)
There is a real cost to supporting old architectures and associated risk in telling users they can run production workloads on them.
Re:Anomalous CPU utilization on Windows build node caused by...
by badsectoracula on Friday July 12, 2019 @01:50PM
(#20422736)
There is also a real cost to dropping support for software working perfectly fine.
Re:Anomalous CPU utilization on Windows build node caused by...
by asveikau on Friday July 12, 2019 @03:15PM
(#20423537)
When a big company explains away how they are not doing something because of engineering resource constraints, put your skeptic's hat on, it's likely an exaggeration.
Re:Anomalous CPU utilization on Windows build node caused by...
by Razengan on Friday July 12, 2019 @01:36PM
(#20422553)
You can still use emulators on macOS Catalina (the version that drops 32-bit support.)
Re:Anomalous CPU utilization on Windows build node caused by...
by mappu on Friday July 12, 2019 @07:33PM
(#20425468)
Aside from the noticably lower memory usage due to smaller pointers - Microsoft found that x86_32 is the lingua franca for WoA emulation. If all the binaries are x86_64 and there are legal problems emulating it, there might be problems switching Macs to ARM CPUs.