(a general mail on the direction to go in in terms of compiling for Windows, but mentions of dropping x86 (ie. 32 bit support) appears later on.
- Almost all systems in the last 10 years are 64 bit by nature or are 64 bit capable
- The maintenance overhead (stemming from the many libraries that Blender uses) is rising fast to keep 32 bit support going, as some throw errors or have other bugs when compiled for such builds.
- Some features don’t work well or won’t work at all with 32 bits anyway (I can’t imagine trying to use microdisplacement with only 2 gigs of RAM available), this will include important 2.8 features like Eevee.
- The percentage of Blender users with 32 bit machines is declining rapidly (now at 15 percent or under), far less than what it was just a few years ago.
- Dropping support will allow the core team to remove many workarounds and make the code cleaner (which also means better and higher quality code maintenance).
It will suck a little for those who are holding out on 32 bits for one reason or another, but they figure that the move will most likely hit schools that use Blender, in which 2.79 will always be available until the machines are upgraded. I imagine this could be the same as when XP support was dropped, needed, but some users didn’t like it anyway.
That’s not to say that people will suddenly need to spend big for a Blender-capable system, as the PC requirements are still pretty conservative as far as 3D applications go. Is this a good move to make now or should it wait until sometime later?