Water consumption of a data center is not a real thing. You don't just consume water. You need it to move heat and you don't need it to remove heat by vaporization.

You can easily use this heat if you actually wanted to do so by heating houses close by or for chemical processes.

Its a legal issue.

And its very resource heavy to put anything in space...

I don't get it. I really don't.

You can calculate the minimum cost, you can calculate heat, maintenance and probably also the expected failerrate for the hardware.

But even if the failerrate is something you need to figure out, that would probably some R&D thing which you would test and verify in a very small and cheap setup.

Same stupid shit with the mirror in space which will send sun back to some PV panels on earth.

Cool stuff in a non capitalistic system but otherwise it just shows that plenty of people have too much money to invest in weird things without understanding it at all.

So i setup everything to do this on my github with their code and publish it on my package.

And you don't think this is stupid?

The problem is the critisim how they act and even if they release everything and its just building the image, you can't trust another source to upload the image someone else has build with this file. So now everyone has to build the same image.

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 they do not trust random companies.

There is a difference between having the official Min.IO image with a stamp of approval vs. forked repos with their version of the same image. The only thing fixing this kind of issue is a fingerprint and build caches.

They are removing the official container images because 1. this is the magic source of running your software in helm charts etc. so now you need to act 2. in some companies you are not allowed to use random container images

And you are complelty ignoring my arguments. Its not entitlement if a companies product becomes the industry standard due to Open Source and then doing a rug pull like this.

Company does a rug pull because they are unable to make a proper business out of it and leaves the community hanging dry.

Removing the container image build step, which was ALREADY THERE, and doing this internaly only, is the gatekeeping they are now doing.

Its like 0 effort to provide these images.

And yes pricing pages like this is always the same: You don't get any deal below 1k / month minimum because they have some pre-sales people and a payment pipeline which doesn't work for anything small or startup like.

Somehow i don't get MinIO anyway. They got over 100 Million of investment for an S3 system. Its basically a done product. Its also a typical 'invest once build it once, keep it running' thing which can easily be replicated with a little bit of investment from other companies.

I have no clue how they ever got valued over 100 Million.