3 ms·
After thinking some more, if what you're saying mostly boils down to "there are serious issues with open core cloud offerings" then I agree. I work on embedded
by ahepp 4y ago
After thinking some more, if what you're saying mostly boils down to "there are serious issues with open core cloud offerings" then I agree.
I work on embedded products, so for my purposes open core usually means "you're getting free beer, but you might not get free updates". We've also paid for commercial licenses of dual-licensed projects and I think that model works pretty well.
Once we're talking about services, if you're not willing or able to operate the service yourself (at the scale you need...) then the open core seems pretty useless as a check on the company's ability to squeeze you for more cash.
On the other hand, it doesn't seem to me like explicitly commercial services solve those problems. Just because a closed source service has a pricing model I accept as fair today, doesn't mean it will tomorrow. But I guess there's something to be said that there was never any pretense otherwise.
- imtringued 4y ago>Once we're talking about services, if you're not willing or able to operate the service yourself (at the scale you need...) then the open core seems pretty useless as a check on the company's ability to squeeze you for more cash. But if you aren't willing, then the service provides value and if you aren't able to, then there is the conflict of interest in that the opencore company might sabotage scaling the opensource version but if we ignore that possibility (after all, you should simply avoid the product, if the opensource version is inferior) then you are again paying for the value of someone else taking care of your problems. Calling this "squeezing" is strange.