Linked by Thom Holwerda on Mon 7th Aug 2006 16:47 UTC, submitted by anon
Thread beginning with comment 150243
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2006-03-20
application can mostly be designed like that but some shared library are considered common enough among dev.
static linking is nice and fast but is not considered as disk space wise. Plus an OS panel for install/uninstall is quite common and useful when wisely designed ( see : package manager in most linux distros ).
dotNet doesn't solve the problem but help with the commonly known 'dll nightmare' where shared library version are overwritten by older version