It's built using Rust and React Router.
Just playing around with it
121–130 of 585 posts
It's built using Rust and React Router.
Just playing around with it
Earlier quoted context omitted.
There is absolutely nothing malicious or suspicious about deciding not to provide docker images or binaries. Doing so does not hide or guard you against CVE's, which are entirely unrelated to such optional processes. Building minio is not only trivial, but is standard procedure - the latest release is in my distributions standard package repo, and they would not use prebuilt binaries. If you want that dockerized, the…
> I can't stand the entitlement people (everyone, not one particular person) feel when they are provided things for free. Does it make you less frustrated to remember that humans are pattern recognition machines and our existence is essentially recognising and adapting to patterns, and so when someone does something repeatedly - regardless of if they're doing it for free - humans will recognise a pattern and adapt to…
Earlier quoted context omitted.
"That expectation does not entitle anybody to anything though." This is true legally, but not otherwise (socially, practically) "That is their decision. Without any contract or promise, there is no obligation to anybody." Again, true legally, but IMHO a really silly position to take overall. Imagine I provide free electricity to everyone in my town. I encourage everyone to use it. I do it all for free. I'm very caref…
Did you read the comments on Github (linked by the title)? So many commenters are just plain rude. They got free value for along time. Someone giving the free value decides to allocate their time otherwise. And the long-time receivers of the free value now cannot behave. And you seem to make excuses for them... It's just rude to behave like that after having enjoyed gifts for so long. They behave like spoiled childre…
It's an Open Source project - I don't understand what people are complaining about. Noone is entitled to receive free Docker images. I'm sure if there is enough demand, someone else who is trustworthy will step up and automate building them. What I'd like to complain about instead is the pricing page on the Min.io webpage - it doesn't list any pricing. Looking at https://cloudian.com/blog/minios-ui-removal-leaves-org…
When you always published and built Docker images for the public you are creating an expectation, people will rely on that and will chose your software based on that expectation. You suddenly deciding that you won't be offering updated Docker images especially after a CVE and with no prior notice (except a hidden commit 4 days ago that updated the README) is approaching malicious-level actions. If they truly cared ab…
Earlier quoted context omitted.
> When you always published and built Docker images for the public you are creating an expectation That expectation does not entitle anybody to anything though. > people will rely on that and will chose your software based on that expectation That is their decision. Without any contract or promise, there is no obligation to anybody. > You suddenly deciding that you won't be offering updated Docker images […] is appro…
Have you not seen some of the replies at the link? For example: "You are joking ?! The commit about source only is 4 days old (9e49d5e) We are currently paying for a license while using the open source version, you already removed the oidc code from UI console and now docker images. We are not happy by this lock-in. We will discuss this internally, but you may loose a paying customer with this behavior."
Earlier quoted context omitted.
When you always published and built Docker images for the public you are creating an expectation, people will rely on that and will chose your software based on that expectation. You suddenly deciding that you won't be offering updated Docker images especially after a CVE and with no prior notice (except a hidden commit 4 days ago that updated the README) is approaching malicious-level actions. If they truly cared ab…
> When you always published and built Docker images for the public you are creating an expectation That expectation does not entitle anybody to anything though. > people will rely on that and will chose your software based on that expectation That is their decision. Without any contract or promise, there is no obligation to anybody. > You suddenly deciding that you won't be offering updated Docker images […] is appro…
When a restaurant which you've been going to for years one day decides to serve you your favorite meal with a bit of poop on the side, do you not have the right to be upset about it? They're not under any obligation to serve you meals you're happy with. There was no contract or promise. The fact you're paying for their service doesn't buy you these rights either. Those are just the terms of service both parties have agreed to.
Similarly, open source software is much more than a license. There is a basic social contract of not being an asshole to users of your product, which is an unwritten rule not just in software and industry in general, but in society as a whole. The free software movement is an extension of this mindset, and focuses on building software for the benefit of everyone, not just those who happen to pay for it, or those who meet your specific criteria. Claiming you support this philosophy, while acting against it, is hypocritical, and abusive towards people who do believe in it. And your point is that that people who complain about this are entitled? Give me a break.
If you want to place restrictions on how your software is used and who gets to enjoy it, that's fine, but make those terms explicit by choosing the appropriate license and business model from the start. Stop abusing OSS as a marketing tactic.[1]
I am also so confused as to what MinIO is now. All I see on the website is AIStor - have they dropped the "S3 Alternative" Marketing and went full AI?
Earlier quoted context omitted.
Do you have a link? I want to read more about that. Did they interpret any use as deriving from minio?
They changed their public guidance at this point, but you can still find references to their approach to AGPL quoted here: https://news.ycombinator.com/item?id=35328316 > "When MinIO is linked to a larger software stack in any form, including statically, dynamically, pipes, or containerized and invoked remotely, the AGPL v3 applies to your use. What triggers the AGPL v3 obligations is the exchanging data between the…
So no matter what they claim large parts of the codebase are still apache2.
https://render.com/docs/deploy-minio
Hopefully this will finally push Render to build their own S3 wrapper.