3 ms·

The first 64-bit Macs came out 16 years ago. The first 64-bit Intel Macs came out 13 years ago. The 32-bit to 64-bit transition on the Mac has not been an abrup

• Wowfunhappy 7y ago
  I think we're looking at this the wrong way. The reason Microsoft killed 16 bit support (In 64 bit editions of Windows) is that very few people were actually running 16 bit apps at that point. Where Microsoft made a decision based on what their users were actually doing, Apple has a made a decision based on what it wants their users to be doing. The amount of time isn't really relevant. If lots of your users rely on 32 bit software, you should put in the effort to make them work. Apple products are expensive, and I think it's reasonable to expect this in return.
  • sarbaz 7y ago
    The true reason is that intel didn't support coexistence of Virtual 8086 mode with 64-bit mode. So adding 16 bit app support would require loads of work to get it working as part of a 64 bit OS. Regular protected mode code has built in support that allows easily running 16 bit apps, so maintaining compatibility was a no-brainer. The moment the trade-off changed, Microsoft decided to drop support for 16 bit apps. Personally, I don't mind that very much, because dosbox is a great product that bridges the gap perfectly.
    • LocalH 7y ago
      Really, all they'd have to do is drop a v86 emulator into NTVDM. There actually exist a handful of projects attempting to bring emulated 16-bit support to 64-bit Windows, including one that's based on that leaked Windows source code (which apparently had a copy of the CPU emulator they used on other platforms back when there were actually non-Intel builds of Windows).