Multiple libs and apps per repo #48
Description
There are numerous (actually, majority) of end-point projects (projects that are the end result) requiring to host multiple libraries and multiple applications.
For example, majority of production software is comprised of N in-house libs, M apps and P tests.
This structure does not fit any of those needs. At best, it fits well with (logically) single entities like libraries. But it also fails there too, for a tad bigger projects, like curl for example, which has at least one lib and one app.
Inability to clearly distinguish between logical entities in any folder-based structure is a big red flag. That's not really a structure, that's more like a glorified convention.
It defeats one of the core purposes: ability to navigate the folders structure without prior knowledge of a convention. It fails the understandability and compartmentalisation from the list of goals.