The difference is this one (layerfs) was vibe coded™ and the other (btrfs) is battle tested in mission critical systems for years in the Linux kernel and used by many companies in the SNP 500.
Do not be fooled by the "vibes" of the website design which many here are. If it is too good to be true, it most likely is.
That's what I was concerned about. An unstable filesystem is worse than no filesystem at all; I'd really like to switch to bcachefs but it simply needs to have a few more years under its belt before I'll be comfortable with it (particularly for some of its best use cases, where it becomes responsible for backups).
Been there (16 years ago), done that (15 year ago), patented it (13 years ago) :) almost the same name too.
https://www.usenix.org/conference/usenix-atc-10/apiary-easy-...
https://www.usenix.org/legacy/event/lisa11/tech/full_papers/...
https://patents.google.com/patent/US8589947B2/
[dead]
Here’s an alternative that runs on your browser: https://nicobrenner.github.io/lossy-git/demo.html
PS: it’s just a fun play on memory/storage and AI. Hope you enjoy :)
This was more interesting/amusing than the OP!
Dumb javascript is preventing me from seeing the footer, by scrolling back up to some content it thinks I shiould see.
Kudos. We did/built something internally to solve similar-ish problems https://www.shayon.dev/post/2026/283/versioned-filesystem-fo...
How is this any different than something like btrfs?
Or this https://arxiv.org/html/2602.08199v1
The difference is this one (layerfs) was vibe coded™ and the other (btrfs) is battle tested in mission critical systems for years in the Linux kernel and used by many companies in the SNP 500.
Do not be fooled by the "vibes" of the website design which many here are. If it is too good to be true, it most likely is.
That's what I was concerned about. An unstable filesystem is worse than no filesystem at all; I'd really like to switch to bcachefs but it simply needs to have a few more years under its belt before I'll be comfortable with it (particularly for some of its best use cases, where it becomes responsible for backups).
I would not trust btrfs with anything mission critical.
> is battle tested in mission critical systems for years
And still crashes and corrupts filesystems all the time.
(I have one server platform where just doing `insmod btrfs` immediately locks up the server, hard, without even any kernel panic or log message.)
How recent is that code?
[flagged]
[flagged]
[flagged]
[dead]