3 ms·
You also can't pay some one else to host it for you. If you have to fork it for any reason, you will be stuck hosting it yourself, even if there is a large gro
by ensignavenger 5y ago
You also can't pay some one else to host it for you. If you have to fork it for any reason, you will be stuck hosting it yourself, even if there is a large group of folks working together on the fork, everyone will have to host it themselves to use the fork, at least for several years until the code becomes open source. Beware vendor-lock-in.
- beagle3 5y agoI don’t consider this vendor lock in; more other-vendor lock out. Which is not to say it is necessarily better or worse - it’s just different. For a company with internal IT or IT capable people, that’s a small hurdle if running the software is not too hard. For a company with all IT outsourced, this is a deal breaker. It will likely stop the behemoths (AWS, GC, Azure) from capitalizing on that product though.
- helloguillecl 5y agoThanks! But does this prevent me from hosting it on say, an instance on Google Cloud? What's the wording that would prevent that?