An interesting perspective. A late youth hobby of mine was being active in a coding community that wasn't open source, it was "lost source": based around a pie

An interesting perspective. A late youth hobby of mine was being active in a coding community that wasn't open source, it was "lost source": based around a piece of freeware that was literally lost to a local storage hardware malfunction. But it had an API and a decade of stability (as in lack of API change, not lack of crashing unfortunately) and that caused an amazing amount of creativity, cooperation and so. Perhaps this is an inherent weakness of open source: it's always easier to accept one more feature PR than committing to an API that remains sufficiently stable for that feature to happen in an isolated module. I'm not saying that its always better to strive for the API instead of inclusion, it's a weakness as much as it is a strength, but chances are many situations where separation would have been better will be missed. It's a cultural bias.