5 ms·

How about we stop mangling metaphors and speak clearly? Paying for software and the licensing terms are independent concepts. We pay for OSS software for the

by steego 5y ago

How about we stop mangling metaphors and speak clearly? Paying for software and the licensing terms are independent concepts. We pay for OSS software for the projects where we find it advantages for us to have access to and contribute to the source code. We customize it, we fix bugs but also benefit from bug fixes done by the full-time developers who we pay to support it. We also control how it’s hosted. We also use and license a bunch of other software where we never want access to its source control. We don’t care if it’s closed source and sometimes we prefer that we don’t host it and manage the IT resources.

oliwarner 5y ago
You don't appear to value independence and autonomy, which is why I'm having such a hard time reconciling what you're saying. While I might not actually want to immediately inspect the source of software we rely on, I might need to later on. We might have artistic differences to the direction of the product. We might need to change or adapt it after we have grown. The pricing structure might change dramatically The SaaS might get bought, retired, hacked, DDoSsed. International law might change meaning we can't use it due to its servers' locations (eg GDPR hassles). Our customers might need security audits that the service is unwilling to go through for us. The reasons for possibly needing to spin up your own instance of the software are broad and dynamic. And they're not stretches. I've migrated to self-hosted versions of things for more than one of these reasons. It seems odd that you would say you'd "never" want that sort of freedom. Don't build your castle on somebody else's land, and all that.
- steego 5y ago
  I value autonomy and independence for the right things that provide us a competitive advantage. I don’t value autonomy and independence for fungible services that are distractions to our mission. For those, we prefer SaaS solutions. Not everything is part of your castle.

by steego 5y ago

oliwarner 5y ago

You don't appear to value independence and autonomy, which is why I'm having such a hard time reconciling what you're saying. While I might not actually want to immediately inspect the source of software we rely on, I might need to later on. We might have artistic differences to the direction of the product. We might need to change or adapt it after we have grown. The pricing structure might change dramatically The SaaS might get bought, retired, hacked, DDoSsed. International law might change meaning we can't use it due to its servers' locations (eg GDPR hassles). Our customers might need security audits that the service is unwilling to go through for us. The reasons for possibly needing to spin up your own instance of the software are broad and dynamic. And they're not stretches. I've migrated to self-hosted versions of things for more than one of these reasons. It seems odd that you would say you'd "never" want that sort of freedom. Don't build your castle on somebody else's land, and all that.

steego 5y ago
I value autonomy and independence for the right things that provide us a competitive advantage. I don’t value autonomy and independence for fungible services that are distractions to our mission. For those, we prefer SaaS solutions. Not everything is part of your castle.