Live data from Hacker News

MongoDB's Server Side Public License Is Likely Unenforceable

processmechanics.com

131–140 of 245 posts

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#131
post #74

It's hilarious to me that out of all the problems with the way MongoDB works it's the license, of all things, that gets a strong reaction from the HN crowd that says, "I'm never using that!"

MongoDB's technical problems are so well known that it's boring to bring them up again.

Mongodb is like Marmite, half tbe world loves it, half hates it, go figure.

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#132
post #70
post #34

Earlier quoted context omitted.

I'm sure that there are tasks for which non-relational stores might be better suited, but pretty much anything MongoDB does, Postgres does it better and in a more performant way (esp after the optimizations to the JSONB data type in the last few major releases).

This is a very bold comment, explain how you scale write, do HA in pg?

https://github.com/citusdata/citus

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#134

Absolutely. This license change takes it completely out of the contention for anything I would have previously considered it for. Can you imagine if Nginx said you had to release any software you run behind it as FOSS?

The SSPL does not create that obligation.

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#136

Yeah, I'm not necessarily opposed to the general spirit of what they're trying to do here, but this license just doesn't make sense in practice. Now that I've had more time to look at it, I'd really recommend that everybody stay the f%!# away from MongoDB. This bit in particular really hits the nail on the head: Let's assume that it is ok somehow to pass forward other open source software, solving that problem. What…

Hmm ... Would this technically be the ultimate Stallman dream?

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#137
post #40

Earlier quoted context omitted.

Of course they’re entitled, but I’m also entitled to say I think this move was either idiotic or malevolent. I’m unsympathetic to the “oh no the cloud” mindset. I’ve worked at companies that have made on-premise patches to FOSS since the 90s. Can you imagine if Linux required you to make the source available of all software you ran on it? Or MySQL? Or Perl/PHP? I can vaguely see the point of the AGPL for things like…

You use their code for free and call them "idiotic or malevolent" when they make it harder for you to use their code for free. I can completely understand the frustration of their users if this move makes their life harder but it's still pretty entitled of you to insult them because they changed the license to something you don't like. It's perfectly understandable if you decide not to use their software because you…

You use their code for free and call them "idiotic or malevolent" when they make it harder for you to use their code for free.

MongoDB is little more than mmap() attached to a socket. They would be nowhere without piggybacking on a million lines of other people’s free code.

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#138

Earlier quoted context omitted.

Try paying your rent and grocery bill with “participating in a rich culture of shared work”. It’s just as much of a joke as “pay you? It’ll give you exposure!” frequently expressed to creatives. It’s clearly not mutually beneficial when one side is reaping outsized rewards (and not at all ashamed about it), and your example of small contributions to vim and python is disingenuous; we’re talking about entire software…

Did Redis, Elastic, Mongo et al pay for Linux development, or glibc, or their text editors, or compilers, or ...? Why should they get the financial benefit from building on top of others' donated work - and claim to be an equal participant in the FOSS ecosystem - and then be peeved with others expect the same in return? If Mongo were a closed, proprietary product who wanted to be paid, sure. I happily pay for Apple s…

Situations change. What you get for free today, you are not guaranteed to get for free tomorrow, nor should you feel entitled to continue using a tool previously provided for free.

This is absolutely no different than commercial vendors who change pricing or licensing terms year to year (ie “we no longer offer an on prem version; SaaS only now; last year you paid $100k, this year our price is $200k”). You’ve just been anchored to an unusually low price previously.

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#139
post #62

Only a data point here -- after I read about this license change on HN, it took me about 2 hours to struggle over the issue, discuss with my team, and switch from MongoDB to PostgreSql. We are very lucky in that we were into this project for only two months, prototyping and learning the ropes with MongoDB schema. With PostgreSql now, everyone feels secure in a familiar territory. Yes, we have to make changes and its…

weary (tired) -> wary (concerned) not nit-picking, just attempting to help other readers who aren't native English speakers

Thanks for saying it right. This will help me remember.

Re: MongoDB's Server Side Public License Is Likely Unenforceable

#140
post #84

Remind me of that one time when they went berserk on every tooling vendor using the name « Mongo » in their product name : RoboMongo,MongoGUI etc... they all received a legal notice to remove the name mongo from their product. This was probably one of the most evil thing have seen in the open source industry . Most of those vendors were open source with paid premium features or donation. After receiving their legal n…

I had no idea that's why it was renamed to Robo3T so confusing. Man what a way to bruise people trying to help.
Post reply on HN