2 ms·

I think this gets tricky if their source code uses other proprietary software that can’t be open sourced. So in practice open sourcing would not be an option.

I think this gets tricky if their source code uses other proprietary software that can’t be open sourced. So in practice open sourcing would not be an option. I could also imagine a common situation where there was some complex integration with various third party like OpenAI where it wouldn’t be that easy for users to handle themselves.

toss1 2y ago
For sure, there will be edge cases and such as you describe. That is no reason to not do it. 1) resolve them in favor of the customers/users. If it is required to use it, release it, and anyone is free to hack. If it integrates with some 3rdPty service, they'll pretty quickly update their TOS to prevent such risks to their codebase, so it won't be an option. 2) it'll encourage corporations selling products to use modular and local-first design. If the product works by itself, local-first, and using a software package delivered with the product, and they sell an ADD-ON cloud-based service, they'll have zero problems. They can discontinue the ADD-ON cloud service at will, and people can still use the original product as sold.
datadrivenangel 2y ago
The classic example is deep use of cloud services. If the whole thing is built on AWS services, you won't have a meaningful app to deploy. Or if they use proprietary assets from somewhere like unity.