←back to thread

672 points LexSiga | 1 comments | | HN request time: 0s | source
Show context
mattbee ◴[] No.45667259[source]
They abandoned documentation (edit: for the open source codebase) a couple of weeks ago - that seems more significant.

From their Slack on Oct 10:

"The documentation sites at docs.min.io/community have been pulled of this morning and will redirect to the equivalent AIStor documentation where possible". [emphasis mine]

The minio/docs repository hasn't been updated in 2 weeks now, and the implication is that isn't going to be.

Even when I set up a minio cluster this February, it was both impressively easy and hard in a few small aspects. The most crucial installation tips - around 100Gb networking, Linux kernel tunables and fault-finding - were hung off comments on their github, talking about files that were deleted from the repository years ago.

I've built a cluster for a client that's being expanded to ≈100PB this year. The price of support comes in at at slightly less than the equivalent amount of S3 storage (not including the actual hosting costs!). The value of it just isn't that high to my client - so I guess we're just coasting on what we can get now, and will have to see what real community might form around the source.

I'm not a free software die-hard so I'm grateful for the work minio have put into the world, and the business it's enabling. But it seems super-clear they're stopping those contributions, and I'd bet the final open source release will happen in the next year.

If anyone else is hosting with minio & can't afford the support either :) please drop me a line and maybe we can get something going.

replies(6): >>45668446 #>>45668529 #>>45668617 #>>45670374 #>>45670759 #>>45672247 #
jamespo ◴[] No.45668617[source]
With 100PB clusters being built and not a cent going to them, you can see why minio has gone this route. I wonder if they will be "valkeyed"? Not by AWS presumably.
replies(5): >>45668679 #>>45668757 #>>45669902 #>>45671591 #>>45671944 #
nilamo ◴[] No.45668757[source]
That's a strange mindset, IMO. I'd be pissed if I had to pay $0.10 every time I turned a rachet, and it's weird to expect companies to have usage-based monetization on the tools they've made for others.
replies(3): >>45668851 #>>45669006 #>>45672397 #
serf ◴[] No.45669006[source]
did you buy the ratchet?

that's why you'd be pissed.

replies(2): >>45669718 #>>45670769 #
protonbob ◴[] No.45669718[source]
If you were given the ratchet and then someone wanted to charge you every time you use it you would also be pissed.
replies(2): >>45670513 #>>45670775 #
palmotea ◴[] No.45670513[source]
> If you were given the ratchet and then someone wanted to charge you every time you use it you would also be pissed.

People gotta eat. If someone's making valuable tools and giving them away, they still need to get paid somehow. If people aren't voluntarily tipping them enough, then something's gotta give.

There have been too many stories of open source developers basically burning themselves out for years, then it comes out that they're barely scraping by and can't take it anymore.

replies(5): >>45670729 #>>45671225 #>>45671395 #>>45672373 #>>45672490 #
danudey ◴[] No.45671225[source]
The problem then is that you're making a valuable tool and giving it away and then wandering around hat in hand. That's not going to work for anyone. Also, taking away things that you've already given people for free so that they have to pay you to get them back is not going to engender any goodwill.

Unfortunately, the minio devs seem to have fallen into the common trap: make a great OSS project that works and that everyone likes, give it away for free, not know how to make money from it, and then start making user-hostile moves that piss off your users to try to make them customers - and who, surprisingly, do not want to be customers now that you've pissed them off.

It starts to feel more like a protection racket. You've got some great features here, would be a shame if something happened to them. Oh no, your docker containers! Oh, that's a tragedy what happened there, but you know, accidents happen.

replies(1): >>45672499 #
1. palmotea ◴[] No.45672499{3}[source]
> The problem then is that you're making a valuable tool and giving it away and then wandering around hat in hand. That's not going to work for anyone.

That is textbook open source idealism: you give to the community, the community gives back. The problem is a lot of people are moochers, even very rich people who have money coming out of their ears.

> It starts to feel more like a protection racket. You've got some great features here, would be a shame if something happened to them. Oh no, your docker containers! Oh, that's a tragedy what happened there, but you know, accidents happen.

Come on, don't be so uncharitable. It's nothing like a protection racket, which is pure, planned exploitation. This is open source idealism coming into contact with capitalist reality.