Programming thread

  • 📧 If you are an employee of a T1 ISP, US datacenter, or related company please get in touch at josh@kiwifarms.net. I have some questions.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Sneed's Feed n Seed said:
MinIO to the rescue!
Click to expand...
What fresh hell is this?

MinIO's github repo said:
This repository was archived by the owner on Apr 24, 2026. It is now read-only.

THIS REPOSITORY IS NO LONGER MAINTAINED.

Alternatives:

AIStor Free — Full-featured, standalone edition for community use (free license)
AIStor Enterprise — Distributed edition with commercial support
Click to expand...
So it's dead, open-source no longer maintained, and its followup is closed-source exclusively. Fucking Grok is recommending "SeaweedFS" as a replacement, though IMHO if we're spinning up S3-compatible storage I'd rather just go full-bore and set up Ceph's RGW and be done with it (you get CephFS as well, might as well use that too). I lol'd at its other suggestions (Garage and RustFS) because they're both rust-based and we all know what that means (shit quality, and trannies errrrywhere).

Why does literally everything useful go down this same fucking road? This is why we can't have nice things.
 
moocow said:
What fresh hell is this?


So it's dead, open-source no longer maintained, and its followup is closed-source exclusively. Fucking Grok is recommending "SeaweedFS" as a replacement, though IMHO if we're spinning up S3-compatible storage I'd rather just go full-bore and set up Ceph's RGW and be done with it (you get CephFS as well, might as well use that too). I lol'd at its other suggestions (Garage and RustFS) because they're both rust-based and we all know what that means (shit quality, and trannies errrrywhere).

Why does literally everything useful go down this same fucking road? This is why we can't have nice things.
Click to expand...

NIGGER FUCKING FAGGOT

DavidS877 said:
I'll take things I've never seen without doing something stupid for $500, Alex. I push literal terrorbytes through NFS at home with no issues.
Click to expand...

Ninja builds of Chromium
 
Sneed's Feed n Seed said:
Not you, MinIO going away :(
Click to expand...
What I find interesting is nobody (so far) seems willing to step up and fork/rename the open source repo and carry on with it. It's almost as if there's some threat by the old maintainer (the "AIStor" guys) to get litigious or otherwise aggressive if somebody tries to keep it alive while the shitheads poison their flavor with AI and overpriced forced commercialization. Wouldn't want the OG (usable) product to undercut their new garbage, after all.
 
moocow said:
Why does literally everything useful go down this same fucking road? This is why we can't have nice things.
Click to expand...
There's no incentive to work on things for free, especially when it can be exploited by large companies to make more money. Honestly I'd rather have paid software with reasonable licenses (e.g. perpetual per major version) but there's barely any software worth buying.

So much open source stuff is only valuable as long as it's free but isn't worth the price tag when they give it one.
 
moocow said:
Classic Microsoft/IBM FUD. Good to see it's alive and well today.
Click to expand...
That isn't what they are saying, though. There are plenty of examples of a project that is used by loads of people and the developer barely gets any funding or support. OpenSSL used to be maintained by one guy in his spare time until Heartbleed, IIRC.

A lot of people give up. BTW, this happens quite a lot when you freelance or work in ossified organisations. You can't get equipment / time / permission to make necessary changes to reliably improve or maintain some software, but you are expected to make it work somehow.

Eventually people will give up & move on or quietly quit.
 
What I'm saying is Linux should probably just fucking fix NFS or manage their own put/get file store S3 thing. Yes the greybeards do it more better than everyone else, fine.

So why was MinIO so heavily used?
 
DavidS877 said:
This sounds like a you problem. I've run giant-ass production web servers(and database, and other things) off NFS with precisely 0 problems. I think I'm up to 30 years of uneventful NFS use on Linux by now.
Click to expand...

We're doing different things.

My workload that stresses NFS is a SLURM cluster of an old i7 and an old Ryzen 7 that would otherwise be e-waste, running distributed Chromium builds with Ninja. Chromium sucks to build. It is a pathological case of moving gigs of tiny files around fast, and it asks the filesystem to do things a web server should never ask a filesystem to do.

I know this isn't a proper build server. It's me hacking together old boxes. You've never seen this because you're not spewing thousands of files a second over old gaming rigs.

I'm saving up for an AI server that could also handle this trivially, on one box, so meh.

Funnily enough, Google doesn't build Chromium on a network filesystem either. They run it on content-addressable storage with remote execution, keyed by content hash so there's no path or stale mtime to get wrong. Google doesn't bother with NFS either for this lol.
 
Sneed's Feed n Seed said:
We're doing different things.

My workload that stresses NFS is a SLURM cluster of an old i7 and an old Ryzen 7 that would otherwise be e-waste, running distributed Chromium builds with Ninja. Chromium sucks to build. It is a pathological case of moving gigs of tiny files around fast, and it asks the filesystem to do things a web server should never ask a filesystem to do.

I know this isn't a proper build server. It's me hacking together old boxes. You've never seen this because you're not spewing thousands of files a second over old gaming rigs.

I'm saving up for an AI server that could also handle this trivially, on one box, so meh.

Funnily enough, Google doesn't build Chromium on a network filesystem either. They run it on content-addressable storage with remote execution, keyed by content hash so there's no path or stale mtime to get wrong. Google doesn't bother with NFS either for this lol.
Click to expand...
So you are doing something pathologically wrong.
 
You must log in or register to reply here.
Back
Top Bottom