Shared libraries

I believe it's intended for embedded use, where they can update the entire image in one go to keep everything consistent but they may want to add and remove modules depending on the context.

(eg. I could see that being used for something similar to how, as explained by the me_cleaner docs, Intel's UEFI is made of modular blocks and the firmware is updated as one blob, but each motherboard model will have different blocks present and absent... before Intel revised their signing to disallow it, me_cleaner would delete some of the modules.)

Multicall binaries are a horrible hack. Anything there's any security policy in place, running one command means you can run any of them.

Ok, but going back to the libtiff example, we probably don't want a multi call binary that includes every app that wants to process TIFFs.

I really wish something like Microsoft's OLE were more acceptable where we'd essentially have a bunch of methods we could invoke on a tiff object that was handled by a different process.