Lego is general graph structure. Our programs have roughly star topology - bunch of libraries and some control logic that drives it. Good libraries _are_ like s

Lego is general graph structure. Our programs have roughly star topology - bunch of libraries and some control logic that drives it. Good libraries _are_ like snapping Lego blocks. Those have good scope around domain, well designed API and establish abstractions that don't leak. Think sqlite, zeromq, zlib. The central controlling part is too "involved" in domain and chosen tech stack to reuse easily. The software that requires organ transplant just wasn't written to be reused. It is a matter of effort and cost. You cannot just solve your problem and wrap it in a library - you need to take care of all common use cases, define edge case behavior, test, document... It costs a lot more and that price is hard to justify. In the end it's the product that makes money and library is forgotten as long as it does its job. We need to fix the open-source income ecosystem.