Linked by Thom Holwerda on Thu 5th Nov 2009 23:05 UTC
Linux As we all know, Mac OS X has support for what is called 'fat binaries'. These are binaries that can carry code for for instance multiple architectures - in the case of the Mac, PowerPC and x86. Ryan Gordon was working on an implementation of fat binaries for Linux - but due to the conduct of the Linux maintainers, Gordon has halted the effort.
Thread beginning with comment 393361
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

Reduces memory use -

Insignificant when the typical laptop comes with 2gb of ram.

Bugfixes. If a security vulnerability is fixed in a library, every app benefits without having to be updated.

And if the update breaks another app? Shared library systems have their own risk in that they sometimes can't patch a file without breaking another app. This can result in a much longer delay for a patch then you would have with a program that updates directly from the developer.

- Yes, drive space. Many mobile devices still have root filesystem on small fast flash drive.

As I said before small devices take small files. The shared library system isn't needed for embedded development. There are plenty of cell phone operating systems that don't use shared libraries.

And these days, we have many click-and-run installers for Linux available. There is nothing in Linux that prevents you from making them (or makes it exceedingly hard, either).

There is no click-n-run installer that works across all distros and makes adjustments for all version differences. There isn't even a standard "program files" directory among distros. It's a big mess and there is no installer that reconciles it.

The burden of making such an installer shouldn't be on ISVs. They shouldn't have to mess with scripts to determine which distro you are using, which version, which window manager, etc. They should be able to dump the program files and libraries into an isolated directory and not have to worry about dependency issues. Users should be able to install or uninstall proprietary applications with a control menu.

Distros simply aren't designed to do that. They are designed around shared library repositories. ISVs run into endless problems when working outside the repository system. Many end up just treating all the distros like individual operating systems.

This is what the end result looks like:

Most ISVs don't have the resources to support a dozen operating systems that only make up 1% of the market. Even those that do probably decide that porting isn't worth the effort.

Reply Parent Score: 2