What are the problems with a relatively large common library?
- by Sam Pearson
As long as the code in the base library is as loosely coupled as splitting it up into separate libraries, what's the problem? In general, having a lot of assemblies composing a .NET solution is painful.
Plus, when code in one solution needs to be shared, it can just be added to the common library, rather than deciding which common library it should be added to or creating yet another library.
edit: the question comes to me after using Smalltalk for a bit, where all the code is available to use, all the time.