On the other hand, the old windows software in question will most likely actually run. Debhelper is irrelevant: confronted with a package of comparable age on Linux, you'll be digging up the source code and trying to make it build, not merely tweaking the package, with all its ancient dependencies.
Also, your 15 year old statically compiled binary will contain every little bug any of the linked in libraries had those 15 years ago.
An issue that was relevant on the Windows 3.x operating systems and, on an unusually bad day, Windows 95/98. It's irrelevant to what we are talking about here and also kind of a red flag for Linux fanboyism.
This was important at the time. And the whole point of backward compatibility is to allowed old applications (written, compiled and packaged at that time) to work.
Even if the software is open-source and has been repackaged in the meantime, the old version you found on a long-forgotten CD rotting away in your basement doesn't have that. The Windows philosophy is to make sure that this one still works (which is a crazy goal IMO, but an interesting one).
I wish I could run any old software under current Ubuntu. IE: gwibber.
[0]: Like this guy: http://www.tomshardware.com/forum/107534-13-trying-install-g....
It's a requirement. Imagine how many people would have never upgraded to Windows 95 if their Windows 3.x programs didn't work.
Each program Microsoft 'fixes' is additional sales.
Also a good example of inside the box thinking. The reason you need to run a 16 bit installer is the software isn't free or open source therefore a simple recompile with a newer version of debhelper or whatever isn't going to bring it up to modern packaging standards.