You must run a very limited set of programs to not have run a single 32-bit one in over 10 years. Even now, on my 64-bit Windows 10, I open my task manager and see over a dozen 32-bit programs running (mostly background processes). You might be running 64-bit Windows, but WoW64 (32-bit binaries on 64-bit Windows) is used constantly.
Nope, I just don't use Windows. I use Linux and MacOS where, if you don't do anything too out of the ordinary you are in 64bit land 100% of the time. On my Mac I don't see any 64 bit programs running and on Arch everything is pretty modern.
Windows still ships both 32-bit and 64-bit versions, and there are still a lot of people with older devices, such as netbooks, that are running 32-bit versions.
Consequently, when you're shipping software for Windows, it's beneficial to have a 32-bit version to capture that part of the userbase. But since 64-bit Windows will also happily run 32-bit apps, once you have a 32-bit version, there's no particular reason to have a 64-bit one. The only time you get something from 64 bits is when you need a lot of memory, which most apps do not. On the other hand, by having a single version, you simplify the acquisition and installation story for the users, cut your testing matrix in half etc.
I don't play games on my computer but if I did I think that is an OK divergence especially for older titles. This is a web browser we are talking about.
