Why are Universal Binaries/FatElf not part of Linux kernel? [closed]

Question

Apple's concept of universal binaries allow easily shipping a single file containing both 32 and 64 bit versions of a binary.

Although this is possible in Linux using FatElf, FatElf and the concept of universal binaries are not baked in the kernel by default?

What is the reasoning behind this? Why do the kernel developers think its a bad idea to have universal binaries on linux?

Update
I am not looking for discussion. It is given that Universal Binaries are not part of the main linux kernel. I am just asking for the reasoning behind it.

Answer 1

It is given that Universal Binaries are not part of the main linux kernel. I am just asking for the reasoning behind it.

A fat binary is twice as fat as it needs to be on either 32-bit or 64-bit system.

Since it's just as easy to provide two separate binaries as a single one, why would I want to carry the extra fat on my system, or why would you want to force your end-users to download twice as much fat as they need to?

I think the reason MacOS chose to use fat binaries is that they didn't want their end-users to understand whether they are running on a PPC Mac or an Intel Mac.

Linux users don't appear to have a problem understanding whether they are running on a 32-bit or a 64-bit system.