Hacker News new | ask | show | jobs
by jcadam 1889 days ago
The rationale for doing this escapes me. Is minio concerned about one or more cloud providers forking minio and then going closed source with their modifications?

I generally only run minio from the official docker image, so I don't reckon this would affect "normal" usage?
1 comments
zamalek 1889 days ago
> forking minio and then going closed source with their modifications?

Which is somewhat bizarre given that aims to MinIO emulate a closed-source system. Open source businesses usually use AGPL or similar to prevent "Big Cloud" from stealing their business, this is a very strange inverted approach and I can't figure out why.

link
the_duke 1889 days ago
There are many companies that might use and modify a S3 compatible object storage.

The world does not run exclusively on AWS, Azure and GC.

link
zamalek 1889 days ago
Correct, but that misses the point I was making entirely. Running S3/Elastic/API-X wherever you'd like is a separate issue to the kind of problem that Elastic faced with AWS. AWS soaked up a huge amount of Elastic's potential market, because they are so big and entrenched. Only AWS, Azure, and GCP are big enough to do that - and I don't see anyone "stealing" a reasonable degree of S3 customers from AWS by using Minio (let alone any business model that Minio might be exploring).
link