Originally Posted by abf
this is how you know you're a gentoo user. everything is about performance gains.
Heh well while its a good point that is how it sounded, it is for other reasons as well
Personally I have been looking at the possibility of a more 'package' based setup for linux, where you roll a package with staticly linked libraries, I tend to prefer this approach for many things, however I dont think it would work but so well in some instances, thus why I am looking at things like this.
For example the primary reason for Dynamicly linked libs like we have today was originally HD space. People didnt have the HD space for static linked packages. RAM was also another large reason for this so you only had to load in one set of packages into the RAM and conserve the limited amount you had.
Now with HD space that is a non-issue for most people these days, a simple 80 gig HD will make this a non issue for most people, and to be honest 80 gigs is small on a desktop these days, even if it is approaching standard on a laptop. Most people fill these up with video/audio/data and not their software anymore.
RAM is getting to that point nowadays as well to be honest. take for example your setup, 4 gigs. out of curiosity what do you do that you come even close to filling that?
For some people they still need as much RAM as they can get, in particular this tends to be the AV folks like myself. But audio, on a lower scale, not feature film, is approaching a point where there will be more ram than is needed for sequencing. 16 Gigs of ram is very possible these days and would be great for, say a multi gig sample set for live performance, in which case you will only be running a select set of programs anyways.
So anyways after that ramble I guess Video are the majority of the folks that need as much ram as they can get, and even in my limited experience on the topic video tends to only do their video at one time on a machine, typically they arent running much else so they wouldnt lose much either.
Advantages of static linking mean easier installs and dependency issues sorted out typically. If you can staticly link against the majority of your libs then distributing binaries means a greater compatibility without solving dependency issues hopefully. Roll your binaries into a packages that can be distributed, dynamicly linked against Kernel and OS(XWindows for example, though technically it isnt an OS) libs I suppose but things like say ffmpeg, or libfft, or half a dozen others could all be staticly linked so that the end user wouldnt have to worry about them nowadays, those libs arent that large on average I dont believe, and the majority of them you will probably only have so many programs running at the same time that use them(Think 1 here
unless you are on a specific type of platform.
Which in my rambling makes me wonder if platforms couldnt be set up to dynamicly link against certain packages that get used often (libfft on audio boxes for example) but statically link against other packages.
Updates for portage system maybe?