|
|
|
|
|
by tejasbaldev
824 days ago
|
|
Could you expand on ''bait & switch'' What exactly is the material impact on a developer with this licensing change? There is a tendency these days to sensationalise things without getting to the bottom of it or even reading the whole article. What did the OSS Redis project promise a developer that it is not going to deliver in the new licensing model? |
|
It also means that if the people providing the software decide to change the deal to something that is too onerous for me to accept, I have options that don't disrupt the continuity of my business.
If I no longer have those rights, I'm no longer willing to rely on this software.
Unfortunately, it's far from trivial to rip Redis out of a running application environment and they know that.
This kind of change feels like a bait & switch to so many people, because it is a bait and switch.
Now that it has been integrated, and could cost hundreds of thousands or millions of dollars in labor to rip out, they change the deal.
We've been reassured for many years that this is OSS and it will always be OSS and many people relied on that assurance to place a hard and expensive dependency on this software.
That is a betrayal of trust and it's hard for me to understand how people aren't seeing it that way.