I'm not really focused on the older programs -I'm looking at 64-bit OS/2 the way Microsoft looked at 64-bit Windows.
</silence>
We may need 64-bit for a 64-bit browser. That's it. And maybe for a 64-bit compiler for at least one user, to compile such a browser. If you'd expect that people want to throw away 20+ years of investements, if anything of time, to browse, then they may as well throw away their software now and start using a 64-bit browser for your 64-bit Windows. I don't really care what your private focus is, but then I'd suggest to throw away "the older programs", i.e. everything for 16- and 32-bit OS/2, and start using whatever already existing 64-bit OS with a 64-bit browser software. So it's not the best point of view ever.
I don't need nor mind 64-bit APIs, but I'd prefer an inclusive strategy instead of yet another lazy it-works-for-me strategy to reduce the size a small community. If someone likes your approach, then delete all "older programs" you've got now, start using any 64-bit OS, and pretend to be happy while browsing with a 64-bit browser.
Regarding 64-bit-APIs, I have no huge files myself, is that it would be nice if it was easier to always support huge files with "older programs", without having to write onesr own LONGLONG-code. Now 2 GiB often is the implied limit, just because it's too hard to support DosOpenL() for a few files of a few users. But we don't have to discuss this here, because "old programs", including but not limited to some older compilers, is not your focus.
<silence>