181–190 of 585 posts
Earlier quoted context omitted.
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.
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.
I think Minio is the only Go client for S3 API and S3-compatible APIs. I cannot say I liked using it, but I had no choice. Nowadays I run my own file storage with my own API, so I no longer care. But if anyone wants to run their own file storage(so not a client), there is https://github.com/seaweedfs/seaweedfs
They don’t owe you anything.
Earlier quoted context omitted.
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.
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.
that's why you'd be pissed.
THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM *"AS IS"* WITHOUT WARRANTY OF ANY KIND
I personally think this is a better option than migrating from an open source license to a source available and I would like more project adopt this approach from the beginning of their projects, to set people's expectation right.
Keep in mind this is the same project that removed all useful functionality from the included web UI in the community edition with the excuse that it was too much effort to maintain. This is another case of VC-funded companies pulling up the ladder behind themselves.
Earlier quoted context omitted.
> Its like 0 effort to provide these images. I love it when entitled folks both expect to use someone else's work AND immediately downplay someone else's effort (no, I am not affiliated with Min.IO, just saying if you are scared of building a docker image yourself, maybe you should not downplay someone else's effort).
I'm not scared at all and could care less about building the image myself. I'm also not 'entitled' because i'm doing this for another open source project we are now maintaining. Just to be clear: THEY already have to maintain the docker image and it makes it less secure for EVERYONE if the community now needs to either find a new github repo/company building it for them or everyone has to build it themselves because…
Correct, and that's the most worrying aspect.
Item 15 of the license states: THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM *"AS IS"* WITHOUT WARRANTY OF ANY KIND They have no obligations to provide documentation, binaries or anything beyond the source code. I personally think this is a better option than migrating from an open source license to a source available and I would like more project adopt this approach from the beginning of their proje…
The license establishes the limits of legal requirements and responsibilities. It doesn't shield you from criticisms and people being annoyed with you.