291–300 of 585 posts
Surprised by the entitlement of some people. This was FREE labor they were providing, it was never going to last forever.
Earlier quoted context omitted.
I think you are digging in a little too hard here. If someone offers a capability that you don't have, and you build that into something you use, then saying that they should be ready for it to go away at any time and be happy to have had it, seems a little too much. If there had never been an offer, they would not have built around it, and would have found another solution and, even if harder or more inconvenient, l…
Metaphor I often see in FOSS. You are this hobby painter sitting every morning on Monmartre square in Paris, painting. It attracts people's eyes. They love your work and you become a sensation, going viral. Instagram influencers from around the world just need you in their picture, they say. You just shrug and paint. One day you got bored of Monmartre. Of pleasing the crowds. You want rest, a spot in nature to paint…
And yet, most people who do decide to share their work in public, directly or indirectly reap the rewards of it. They get exposure and recognition, which in turn opens many doors. I'm not saying that exposure alone puts food on the table, but it's certainly not entirely negative. Many people would envy to be in that position.
Your analogy is akin to any public figure enjoying their work, but not enjoying the attention. That certainly happens, but the attention, and all its negative aspects, comes with the territory. That attention might even be partly responsible for getting them to where they are. People in such line of work must learn to live with their choices. Not be surprised when their audience has certain demands and expectations, which may or may not be within reason.
Open source is sick. Everyone wants it (both to maintain a successful project, and to use them) until you maintain a popular project for a reasonable time then your realise you're getting used for fuck all value. We need a healthy way to support open source developers. This isn't working. Companies are taking advantage, and individuals are overwhelmed with choice and have delusional expectations.
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 goi…
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.
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 goi…
>The price of support comes in at at slightly less than the equivalent amount of S3 storage That's absurd. I would be running to NetApp and Dell for competitive object storage quotes then. Haven't done pricing on either one recently but at least a few years ago they were roughly half the price of S3 all in (including hosting costs).
No one other than hobbyists is paying full price on AWS.
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. Agree. But that's not my point. If you start an oss project from scratch and you don't want to provide builds that's fine. If you start your oss project, provide public docker images since the beginnin…
It’s irresponsible to use open source software, be it a docker image or the application itself, if you’re not willing to maintain it or replace it yourself at short notice if what the maintainer is willing to do/publish no longer meets your needs. Don’t like it? Stop being a parasite and pay someone for a support contract.
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 goi…
That does sound much worse than hiding the pre-built images from users. I hope that documentation is archived. There's probably some benefit in documenting those installation tips elsewhere besides Github comments.
I don't see the problem here in theory - if I want to trust something fully I'll build it myself in my own pipeline, often with additional hardening as needed. It only needs scripting out the build process to fit alongside my other code. I even do this for Linux apps like Signal because I want a clean binary that matches the Git tag, packaged exactly right for my system, built with the libraries already in place loca…
> Leaving a known unsafe version as the last release is irresponsible. I think they should have done a better job of announcing this ahead of time (or at all, really); but there's realistically never going to be a CVE-free release to stop on, because the next CVE is just around the corner.
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.
> I wonder if they will be "valkeyed"? Not by AWS presumably Almost certainly not, due to the AGPL license. I know Nutanix got into hot water about distributing Minio so I don't think any big shop will fork it.
I think it is unlikely a single entity would do that. But a coalition of current MinIO users might get together to create such a project, perhaps under the Auspices of a foundation such as the Linux Foundation. Although, I think that scenario would be more similar to OpenTofu than Valkey.
It's absolutely stunning that people actually defend this behaviour! The community is having an outrage - and rightfully so - about a silently discontinued artifact delivery at a very critical time. Which is their opinion and every human being is entitled to have their own opinion and state it openly. It is also perfectly fine to expect a standardised behaviour to continue. However, what is most important is that is…
I don't think the people in this thread have any concept of how much $$$ it costs to distribute a free container that is going to be downloaded billions of times. You are a farmer, not a big fancy profitable one. Your tractor is from 1970 and works great, when it works. Your wife has health problems and can't really help out around the farm much - kids have gone off - so you just do things mostly by yourself. With yo…
Not very much at all. It looks like they're hosting on Docker Hub which doesn't charge for bandwidth. I could create a pro account for $11/month and be able to serve an image billions of times. The compute to build an image is small enough that it can be done at whim on a dev machine.