[ElDji]

I successfully migrated from MinIO to Ceph, which I highly recommend. Along the way, I tested SeaweedFS, which looked promising. However, I ran into a strange bug, and after diagnosing it with the help of Claude, I realized the codebase was vibe-coded and riddled with a staggering number of structural errors. In my opinion, SeaweedFS should absolutely not be used for anything beyond testing — otherwise you're almost certain to lose data.

[MikeKusold]

Seaweed has been around for a long time. I think you just discovered what legacy codebases look like.

[g-mork]

Laughed reading this. We pretend Claude can't code because we don't like to acknowledge what code always turns out looking like, which is exactly what it's trained on

[chrislusf]

(I work on SeaweedFS.)

Haha, you used Claude to find the Clause code.

I used Claude to generate a lot of admin UI pages, saved a lot of time. The core storage engine part I dare not using AI, same as you.

[vimda]

Ceph is the OG. Every now and then different attempts to replace it pop up, work well for some use cases, and then realise how hard the actual problem they are trying to solve is. Ceph always wins in the end.

[Giefo6ah]

Ceph solves the distributed consistent block storage problem very well. But I hardly ever need that problem solved, it's way more often that I need a distributed highly available blob storage, and Ceph makes the wrong tradeoffs for this task.