> Yes, having a user manually choose a binary to download from a web browser is poor, but certainly there are technological solutions to this that are lighter weight than doing a full download of a fat binary for everyone.
In the average application, the binary is only a minor contributor to bundle size, assets are the vast majority of it.
For instance on my system Delicious Library 3 is a 110MB bundle. The binary is under 4MB. Same observation with Keka (30MB / 344K), xACT (15MB / 960K) or unicode checker (10MB / 500K)
Fat binaries were not an issue during the last transition, they're even less so now.
In the average application, the binary is only a minor contributor to bundle size, assets are the vast majority of it.
For instance on my system Delicious Library 3 is a 110MB bundle. The binary is under 4MB. Same observation with Keka (30MB / 344K), xACT (15MB / 960K) or unicode checker (10MB / 500K)
Fat binaries were not an issue during the last transition, they're even less so now.