🚀 go-pugleaf

Charles Robinson writes
> Fat binaries (like those planned for NextStep 486) should solve your  
concern.
> Basically the (incompatable) binaries are packaged together and  
NextStep
> figures out which one to load. Developers will, as I understand the  
current
> situation, be forced to compile on each native system (no cross  
compilers
> will be available for the 486).
> 

In many ways the ideal would be to sell the packages as Fat Binaries,  
but then have a standard diet command that could strip out the binaries  
that you didn't want.

Thus if you bought a 6 unit FrameMaker license, and had it on a network  
with both 486's and Classic Slabs, but no Next Risc Workstations you  
would run 
diet -d 88110 app-folder,
and diet would strip out the 88110 stuff. 
and it would go through that folder looking