My family has been working as teachers and staffers in my town's public school system for almost 30 years. In those 30 years, the school budget has been approved only 28 times. No one wants to pay for education. However, people are more than happy to pay for our HS's absurd sports program. Every year the administration tries to move money from sports to academic programs, but outraged parents always reverse the decision. Last year the administration faced such a budget shortfall that they put a referrendum out to the town - Cut the sport's budget by 50% or cut music/wood|metalshop/arts/home-economics entirely from the budget. Guess which one the people chose?
Besides issues with performance vs size (that others have pointed out), there are also security concerns too.
Suppose you statically compile your program with libfoo version 1.3. Hundreds of people download it and are running it. Later on the libfoo devs find a security hole or other bug in the library and release libfoo1.4 to patch it. Well even if all of your users upgrade to the newest version of libfoo, they will still be vunerable to the bug. Why? Because libfoo1.3 was statically compiled into your app, all your users will have to know that they need to download and install your application again to fix the security problem. THat also means you have to be aware of the libfoo bug and recompile and post a new version of your app.
Thats asking alot of from both the developer and the user dont you think?
In the year 2000, genetic enhancements will make everyone look super beautiful, the downside being everyone will look exactly like one another.
Ahhh... Don't you love conan obrien?
Unix has had library versioning from the very beginning. Shared library filenames specify what version of the shared library the file contains, and when programs load they can request a specific version thru the file name.
And here comes M$ taking the same idea, and adding a point of failure in the form of some binary index of dlls. Jeezz this is just another thing I'm gonna have to fix when my windows friends start having trouble with thier computer. Really unnecessary. Couldn't they have just outright copied the Unix method? At least then they would have done it right.
Slashdot Mirror
My family has been working as teachers and staffers in my town's public school system for almost 30 years. In those 30 years, the school budget has been approved only 28 times. No one wants to pay for education. However, people are more than happy to pay for our HS's absurd sports program. Every year the administration tries to move money from sports to academic programs, but outraged parents always reverse the decision. Last year the administration faced such a budget shortfall that they put a referrendum out to the town - Cut the sport's budget by 50% or cut music/wood|metalshop/arts/home-economics entirely from the budget. Guess which one the people chose?
Suppose you statically compile your program with libfoo version 1.3. Hundreds of people download it and are running it. Later on the libfoo devs find a security hole or other bug in the library and release libfoo1.4 to patch it. Well even if all of your users upgrade to the newest version of libfoo, they will still be vunerable to the bug. Why? Because libfoo1.3 was statically compiled into your app, all your users will have to know that they need to download and install your application again to fix the security problem. THat also means you have to be aware of the libfoo bug and recompile and post a new version of your app.
Thats asking alot of from both the developer and the user dont you think?
Hey why aint gentoo on the list? I guess they're still compiling their response ,p
(PS I love gentoo, so don't go flaming me!)
In the year 2000, genetic enhancements will make everyone look super beautiful, the downside being everyone will look exactly like one another. Ahhh... Don't you love conan obrien?
Unix has had library versioning from the very beginning. Shared library filenames specify what version of the shared library the file contains, and when programs load they can request a specific version thru the file name.
And here comes M$ taking the same idea, and adding a point of failure in the form of some binary index of dlls. Jeezz this is just another thing I'm gonna have to fix when my windows friends start having trouble with thier computer. Really unnecessary. Couldn't they have just outright copied the Unix method? At least then they would have done it right.