>>As soon as they remove the support for Win32, they are obligated to change the name, or they will lose all credibility.

FWIW, VFP is not trapped in Win32: I can compile my VFP apps to x64 today using VFP Compiler. The biggest impediment is that most of the add-ons we rely on are only 32-bit. West Wind, the Sweetpotato flls, etc etc, though theoretically these also can be recompiled to x64 and Chen is offering to assist. The big one is that 64-bit OS no longer comes with OCX for treeview and the like, so you need to purchase commercial options for anything that isn't a native VFP control and generally you'll need to re-do the interfacing code.

For the above reasons as well as the reality that x64 performance generally is slightly slower and memory use slightly greater, in 2015 I see no great purpose in recompiling a GUI app to 64-bit except to prove that you can. Certainly there's no compelling benefit for customers in my customer base and the logic that drove a move from DOS to Windows cannot exist when the app looks the same either way. Meanwhile you only need to look in an average machine's Program Files (x86) folder to see there's lots of 32-bit out there still.

MS has made the smart decision: when it tried to corral people into its mobile Windows option, millions of natural Windows customers marched in a different direction. When it tried to propel people to Vista, it was a monumental own-goal that also tarnished credibility of MS familiars who tried to urge us that everything was wonderful. The customer is always right and if the customer wants to run 32-bit apps, then MS makes the correct decision in making sure they (we) can.