←back to thread

672 points LexSiga | 1 comments | | HN request time: 0s | source
Show context
cduzz ◴[] No.45668391[source]
I haven't used minio in years, and when I did I only fiddled around with it, but my recollection of it is that it's about the simplest build chain imaginable. Install modern golang, build minio, get single binary.

Anyone relying on an opensource tool like minio, needs to look at:

  * organization supporting it
  * the license
  * the build chain
  * who else uses it?
  * the distribution artifact needed for production.  
Once you've looked at that you can decide "is this an anchor I want to handcuff myself to and hope the anchor won't jump into the icy blue deep taking me and my dreams with it?"

If the org behind it ever decides to rugpull/elastic you, what're you gonna do? At least with something like minio, if they're still distributing the source it's trivial to build (and if you can't build it you should evaluate if you're in a position to rely on it).

Let's look at other cool open source things like SigNoz which distribute only docker artifacts (as far as I remember, anyhow) -- if they were to rugpull that people relying on it would be totally lost at sea.

This isn't to say that this isn't poor behavior on minio's part, but I feel like they've been signaling us for a while that they're looking to repay their VC patrons.

replies(2): >>45668452 #>>45670869 #
1. apavlo ◴[] No.45668452[source]
> If the org behind it ever decides to rugpull/elastic you

I love it that you use "elastic" as a verb here.