Re:Examining Windows 1.0 Hello.c
by eddieroger on Monday May 25, 2020 @09:45PM
(#23306684)
Devil’s Advocate counterpoint - being able to still run Win1.0 is evidence of the baggage that Windows is carrying around, and maybe it would do them some good to eventually cull out some old cruft. The transitions will naturally be painful, but how much further and faster could they go if maybe they stopped supporting code from 35 years ago?
[ Parent
| on HN ]
Re:Examining Windows 1.0 Hello.c
by NCommander on Monday May 25, 2020 @10:00PM
(#23306764)
IBM Mainframes laugh at Windows backward compatibility. 50-60+ years isn't unheard of. I actually want to at some point climb that cliff but my next write up is exploring Windows 3.11's networking features, and then Novell NetWare; the Windows one should go up tomorrow on SN, and NetWare next week.
I look forward to the NetWare one!
Have you read an article?
1) It specifically needs the 32-bit version of Windows.
2) It won't run on 32-bit Windows 10 without an additional installation (NTVDM).
I don't see any "baggage" which limits anything, for any "normal" user.
Yep, when trying to learn Windows programming in 2020, you can literally see the geological layers of APIs accumulated over time... It does not make things easy. Not to mention that development on Windows team in MS must be a nightmare...
I wonder if it would be a good idea for them to remove a lot of the old APIs and instead provide a seamless virtualization mechanism for running the old binaries.