5 ms·
The terrifying result of having ABI compatibility with the first commercially successful system of its kind from the '80s. Granted, they aren't doing themselve
by microcolonel 9y ago
The terrifying result of having ABI compatibility with the first commercially successful system of its kind from the '80s.
Granted, they aren't doing themselves any favours with their new straight-jacket style application ABI.
- willvarfar 9y agoYou are trotting out the same tired line without reading the article carefully? ;) This is a regression. The article shows it worked fine up to Windows 7.
- Aeolun 9y ago7 is the best
- option_greek 9y agoRegardless of how many windows/any other OS versions I use later on, I will remember Win7 fondly. Its just so.. less cumbersome. May be the drastic changes that went into its preceeding and succeeding versions have a role to play in this.
- krylon 9y agoThere is this old quote that Algol 60 was an improvement not only on its predecessors but also its successors. The same could be said about Windows 7, I guess. ;-)
- jbg_ 9y agoHow is ABI compatibility with early systems the cause of this bug? You'll note that it wasn't present in Windows 7.
- LeoPanthera 9y ago64-bit versions of Windows 10 (and 8/7 maybe?) are no longer compatible with 16-bit code.
- ripdog 9y agoYep, no 64-bit Windows has 16-bit compatibility.
- deleted 9y ago[deleted]