Photoshop, Visual Studio, Chrome.. you name it. Pretty much ALL executables fall into this category. Unless it's a UWP app.
Almost all modern games will fall into this category.
EDIT: To further explain, You still use Win32 for 64-bit processes. It's just a stupid name.
Converting a Win32 exe using UWP Desktop Bridge is stupid easy though. Older exe with a lot of legacy dependencies may be more difficult or lack of source code. In which case they need a virtualization to run those legacy app.
So even though all games/apps fall into this category most companies could have a UWP build ready very quickly.
It just wraps the app, but underneath still calls those same win32 APIs. If you remove the APIs, "bridged" apps won't work. Hence why TFA mentions that not all win32 API can be removed and it isn't clear which will be.
So "bridging" your win32 app will not somehow make it immune to win32 api going away.
I still encounter a fair numver of new games that are built on DX9, not even DX11.
Brb gonna go play more overwatch.
In all seriousness we complain in the developer community that Internet Explorer and Edge holds back using more modern Javascript yet we make these excuses for OSes.
Almost all programs I use now have a 64-bit executable. If I am using something that needs to run legacy software then I probably don't want the latest version of something to run legacy stuff.
Also the article indicates you can still run 32-bit apps. Most older 32 bit games should run perfectly fine under virtualization. Even then it will be a few years before the majority of Steam user are even using Windows 10 as last I check over 50% were on Windows 7. So by the time gamers shift to Windows 10 i'd imagine their hardware will be more than adequate to handle virtualizing the 32-bit app, I can't imagine there will be much overhead to virtualizing 32-bit apps.