Hacker News new | ask | show | jobs
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?

1 comments

For me, using OSS means that if I bump into a problem, I can fix it and use, and share the fix. Yes, I've created OSS projects and contributed to others.

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.

How do you think your freedom to “fix it and use, and share the fix” is changing? Unless you’re running a Redis hosting service isn’t it business as usual?

I don’t love the direction that the open source world has been moving in but in terms of practical impact on my work this seems to be minimal. I think the easy money during the VC bubble lead a lot of us to get used to high-quality software not having a plausible business model and we’re going to see a lot more of this, which makes me wonder if OSI could come up with some kind of hybrid license allowing maintainers to get paid but not giving up too much freedom. Otherwise it feels like we might see a move back towards closed-source development.