The BSD license in particular seems like a particularly bad way to run a business.
The race to replace Redis
41–50 of 520 posts
Re: The race to replace Redis
#42Engineers have to eat too. Nothing wrong with charging for support. I love passion projects as much as anyone, but there is a reason they are hobbies, and people need to keep a day job. Eventually it does get tiring to do support for free. Edit: Ok. I was talking OSS generally. I guess Redis is being bad actor if they are taking OSS work and running away with it to get the money, and not compensating the contributors…
I think the main issue is bait and switch. You start with a license, get lots of external contributors who are working for free, get ecosystem built around it for free and then change because you want to be paid.
I'm not sure how nefarious this Redis move was. I guess I was assuming any move from 'free', to 'paid', will be met with some outcry regardless of how seamless they can pull it off.
Or in other words, it is always a messy transition?Re: The race to replace Redis
#43Re: The race to replace Redis
#44Engineers have to eat too. Nothing wrong with charging for support. I love passion projects as much as anyone, but there is a reason they are hobbies, and people need to keep a day job. Eventually it does get tiring to do support for free. Edit: Ok. I was talking OSS generally. I guess Redis is being bad actor if they are taking OSS work and running away with it to get the money, and not compensating the contributors…
Re: The race to replace Redis
#45But I feel no such sympathy for Redis nee Labs. It was never their project. They took over stewardship and then effectively stole the project for themselves. They’re not even the dominant contributor to the core product.
Re: The race to replace Redis
#46Re: The race to replace Redis
#47https://github.com/Snapchat/KeyDB
[EDIT] whoops, didn't read the article, went immediately to comments for recommendations since that's what HN is good at IMO.
Re: The race to replace Redis
#48So we as developers don’t have to scramble to replace redis in our SAAS apps and web based software.
This is more about preventing AWS from eating their lunch by providing redis-as-a-service, without paying any sort of compensation to the redis developers.
Redis’ blog post: https://redis.com/blog/redis-adopts-dual-source-available-li...
Re: The race to replace Redis
#49Somehow no one has mentioned KeyDB so: https://github.com/Snapchat/KeyDB [EDIT] whoops, didn't read the article, went immediately to comments for recommendations since that's what HN is good at IMO.
Re: The race to replace Redis
#50Engineers have to eat too. Nothing wrong with charging for support. I love passion projects as much as anyone, but there is a reason they are hobbies, and people need to keep a day job. Eventually it does get tiring to do support for free. Edit: Ok. I was talking OSS generally. I guess Redis is being bad actor if they are taking OSS work and running away with it to get the money, and not compensating the contributors…
I agree. People here always seem to react badly to companies that provide something for free and now want to make a bit of money. It’s weird because they themselves work in tech and have to earn a living to put food on the table. Having no way of making money isn’t sustainable.
It's a company surprising everyone by pocketing the money from other people's hard, unpaid work.