|
|
|
|
|
by mbeex
2310 days ago
|
|
> These are all largely header libraries. That's not even true for boost, no matter if they always advertise that. The lib is also notorious for bad decomposability (using only a subset without installing the whole monster). Not to speak about idiosyncratic naming and build system, making it sometimes hard to include it in meta builds of other libraries and frameworks. In sum: Anyone sensible, regarding different kinds of footprint and dependencies will think twice, before pulling in these kind of libraries. |
|
Boost is better thought as a loose collection of libraries that try to follow some common design principles instead of a single monolithic library.
I can't defend the build system though.