Was that intended as a joke?
No, I'll explain why...
Static linking introduces horrors that are far harder to solve than
any of the issues I mentioned with dynamic linking. You can't patch,
for one thing.
So it doesn't work in all scenarios. It's not perfect, just like anything
else.
But consider that for someone rolling out their own software stack, they
usually have the source code. And if stuff needs to be patched, the whole
thing gets relinked and recompiled. CPUs are fast nowdays, and lots of them
have multiple cores to deal with that.
I admit, for the parts of the OS, this model doesn't work well. But for
individual applications, it works beautifully.
Remember: sysadmins and ordinary users don't have the time or the
inclination to deal with the .so dependency hell, and open source software
introduces exactly that.
People just want to install the software and have it work, in the minimum
amount of time, not be stuck resolving dependencies and installing 56 other
different pieces of software, which introduce 108 other dependencies.
That's the shared object model gone too far, out of control. And that's
exactly where statically linked binaries come into play. It's a complete,
ready to use product, just like it should be. And if you need to patch, just
deliver the whole binary inside of a patch package. There are ways.
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
_______________________________________________
opensolaris-discuss mailing list
[email protected]