Live data from Hacker News

Redis will remain BSD licensed

antirez.com

141–150 of 206 posts

Re: Redis will remain BSD licensed

#142
post #140

Earlier quoted context omitted.

> elasticache is just vanilla redis Only at the interface level. Elasticache is a heavily forked Redis. There's a reason it's several versions behind.

that makes sense. i guess i had just assumed it was laziness. :-) out of curiosity, do you have any idea what their mods might be?

I never bothered to really look into it -- I suspect it's semi-public information. If I had to guess, lots of internal changes to make Redis behave better in AWS's architecture to do with containerization, EC2, S3/EBS, maintenance automation related stuff, instrumentation, etc.

Oh actually definitely some stuff related to their redis clustering system.

Re: Redis will remain BSD licensed

#143
post #110

Earlier quoted context omitted.

That's irrelevant. Nobody is going to read your FAQ. You intentionally created something that tries to muddy the lines between Open Source and Non Open Source. It's dishonest, and deceitful.

You can't abuse anyone like that here regardless of how wrong they are or how you feel they are. Please keep the online shaming culture well away from HN. https://news.ycombinator.com/newsguidelines.html

You're right, and I've edited my post to reflect that.

Re: Redis will remain BSD licensed

#144
post #111

Earlier quoted context omitted.

Yiftach (and Antirez), Please talk more about AGPL. MongoDB has a similar problem, and they solved it by making their product dual-licensed, AGPL + commercial. They then clarified the AGPL to say that in their opinion, it did in fact prevent cloud providers from building managed services around the modules. https://www.mongodb.com/community/licensing/faq The AGPL is lengthy and a bit convoluted, so it's possible they…

Well - I can only say that what MongoDB has is not complete. There are still many holes, and we prefer to avoid them. And of course this doesn't solve the other issue, where developers cannot use AGPL in large enterprises.

But that's kind of the point -- those who live in large enterprises who can't use the AGPL must buy a commercial license. The AGPL is toxic in some places, and its use is a deliberate attempt to nudge people toward a commercial license. Did this not work in your case?

Re: Redis will remain BSD licensed

#145
post #125

Earlier quoted context omitted.

They have different ideologies behind them, but they refer to almost exactly the same class of software. A license that doesn't allow commercial use is proprietary and closed source.

Forbidding commercial use doesn't make something closed source but it does make it proprietary. The compliment of Open Source isn't closed source.

Can you give an example of something that's neither open source nor closed source, or of something that's both open source and closed source?

Re: Redis will remain BSD licensed

#146
post #129
post #108

Earlier quoted context omitted.

There's no need to get personal about it, even when you disagree about licensing. Please don't.

The "what's the clause?" section starts with a plug for the clause's creator - even before answering the question, which seems a bit unnecessary, but I'll edit the post and remove the personal reference. Sorry Dan.

Simply naming someone is not 'a plug'. It's just naming someone.

Re: Redis will remain BSD licensed

#147
post #129
post #108

Earlier quoted context omitted.

There's no need to get personal about it, even when you disagree about licensing. Please don't.

The "what's the clause?" section starts with a plug for the clause's creator - even before answering the question, which seems a bit unnecessary, but I'll edit the post and remove the personal reference. Sorry Dan.

Appreciated!

Re: Redis will remain BSD licensed

#148

I've seen saying for years and years that we're going to see a resurgence of proprietary software. Free software was one of those ideas that spread so successfully that people temporarily forgot that life could be otherwise, which means they stopped caring about the idea, which in turn led to a complacency that, at first, shifted software licensing to a BSD-style permissive model, and now, is starting to allow 1990s…

The baseline is pretty high to call anything a resurgence. I guess by revenue dollar most software is already proprietary, it's just billed as a service or whatnot. Considering all the code inside of companies, it's probably the case that most lines of code are also proprietary.

Revenue is probably not a good measure, as an open source solution tends to reduce market size as measured by dollars spent. From Bob Young, founder of Red Hat:

> The reality is most of our users don’t pay us squat [...] Our business model [showed] that if we had millions of users, we only needed one-tenth of our users to actually find something of value to pay Red Hat for.

> If Microsoft’s earning $40 billion worth of operating system sales, and if we [reduce that to] a $4 billion-a-year market, because nine out of ten of the people that use our operating system aren’t going to pay us, we’re quite happy with a share of a $4 billion-a-year market.

https://growthhackers.com/growth-studies/red-hat-how-they-de...

Re: Redis will remain BSD licensed

#149
This still doesn't sound good. Even I don't like the fact that AWS is extremely bad at giving back to the community but it is not like doing things like this will make people use RedisLabs. Infact, I will be wary of using these modules for the fear of getting locked with a vendor.

I have used both Elasticache and RedisLabs and can say both have their advantages and annoyances. Elasticache is way easier to set up and configure. RedisLabs puts a lot of artificial restrictions which you have to work around. Also, their pricing model is kind of screwed up. The only major problems I have seen with Elasticache are: Locked APIs, no way to scale instance once created with live traffic, A-Z failover sucks and no persistence.

Re: Redis will remain BSD licensed

#150

I've seen saying for years and years that we're going to see a resurgence of proprietary software. Free software was one of those ideas that spread so successfully that people temporarily forgot that life could be otherwise, which means they stopped caring about the idea, which in turn led to a complacency that, at first, shifted software licensing to a BSD-style permissive model, and now, is starting to allow 1990s…

Have you read the Commons Clause license? Do you understand it well enough to back up those absurd claims you're making? People see "oh it's not OSI-approved" and just de-facto assume it's the end of the world. Redis is an amazing piece of open source, BSD software and you're taking a huge dump on it and its author for not complying to your wishes. Friend, have you done for open source even 1/10th of what Antirez and…

Your comment is not productive. It attempts to substitute emotion, misplaced empathy, and ultimately social shaming in place of a discussion of the linguistic and economic issues that this Redis affair is surfacing.

Your post amounts to a ban on criticism, on made on the grounds that it might make people feel bad. It's an attempt to end discussion, not further it. Much like proprietary software licensing, this approach has been tried many times before and has seen limited success.

Post reply on HN