On Thu, 12 Sep 2019 17:58:08 -0400 Michael Orlitzky wrote: > What kind of math would convince you that an idea with all "cons" and no > "pros" is bad? Is "upstream tooling doesn't work without static compilation" or "built packages tend to need exact version matching at runtime to work" ( which necessitates massive-scale multi-slotting, where every version of every packaged "thing" has a co-existing slot ) a problem for you? Having the same problem as static-linking in terms of disk use ( all those different parallel versions ), but adding dependency hell to it , and adding compile time overhead (even if those assets were no-op virtuals, portage overhead is still pretty steep) isn't fun. Not to mention reduced opportunities for whole-program optimization. Yes, In general I'm against static linking, and I really dislike this trend. But when upstreams ecosystem is built around it as a core concept, its really hard to buck that trend.