I’m trying keep xcode chaos under control. Namely, how to reuse my small components/classes between projects. One strategy is to make every class, or tightly coupled collection of classes, in to a static library, each being a spawn of a different sub project with a few targets like unit tests, demos, and, of course, the library.
The way it looks now, I could I see a final app being composed of some custom code, and, say, a couple hundred libraries. That scares me, but should it? Would performance suffer? Are there other limitations to the many-library approach that would make it impractical?
After some offline-discussion, the consensus was that 100s of libraries would not slow down executions, but could be painful during linking.
The complexity of managing lots of libraries, could, of course, could make the solution worse than the disease.