🚀 go-pugleaf

In article <1992Oct27.073704.3336@utstat.uucp> philip@utstat.uucp (Philip  
McDunnough) writes:
> In article <1992Oct26.060414.8580@athena.mit.edu>  
zmonster@athena.mit.edu (Eric M Hermanson) writes:
> 
> [ ]
> >
> >Well Philip, NeXTstep 3.0 can handle things called FAT BINARIES, which  
in 
> >effect let programs be compiled over two or more platforms.  This  
allows
> >developers to include both NeXT and 486 versions in one piece of  
software,
> >while the machine you are using sorts out which code to use (at least  
this
> >is how I understand it).  These FAT programs do not take up much more  
space,
> >either.  Typically a FAT binary will take up only 10-15% more disk  
space than
> >the single machine version.  Therefore, you will not have to buy two  
different
> >software packages for the NeXT and 486NeXT.
> 
> This is wonderful and would be a very big advantage for NeXT. Are there
> developers who have committed themselves to including both the NeXT and
> 486NeXT software packages in the same box? If there were a significant 
> number, then the future for the NeXT (and the developers) will indeed be
> bright.
>  

If most things we hear about fat binaries are true, we will ship  
MetroTools in that format. It would actually be easier for us to just have  
one product to stock, and the benefits to the user aren't lost on us  
either. Clearly it's the way to go.

MetroTracks may be another story due to the PC-specific hardware support  
that it looks like will be necessary. If it's feasable though, it will  
ship in fat binaries too.

Gordon

-- 
----------------------------------------------------------------
Gordon Van Huizen           vox: 619.488.9411  fax: 619.488.3045
Metrosoft                   gvh@metrosoft.com [NeXTmail welcome]
----------------------------------------------------------------