Been there (16 years ago), done that (15 year ago), patented it (13 years ago) :) almost the same name too.<p><a href="https://www.usenix.org/conference/usenix-atc-10/apiary-easy-use-desktop-application-fault-containment-commodity-operating" rel="nofollow">https://www.usenix.org/conference/usenix-atc-10/apiary-easy-...</a><p><a href="https://www.usenix.org/legacy/event/lisa11/tech/full_papers/Potter.pdf" rel="nofollow">https://www.usenix.org/legacy/event/lisa11/tech/full_papers/...</a><p><a href="https://patents.google.com/patent/US8589947B2/" rel="nofollow">https://patents.google.com/patent/US8589947B2/</a>
Here’s an alternative that runs on your browser: <a href="https://nicobrenner.github.io/lossy-git/demo.html" rel="nofollow">https://nicobrenner.github.io/lossy-git/demo.html</a><p>PS: it’s just a fun play on memory/storage and AI. Hope you enjoy :)
Dumb javascript is preventing me from seeing the footer, by scrolling back up to some content it thinks I shiould see.
ShowHN: WoolJ.ai the virtual wool jersey tailor-made for your most special coding agents
How is it v1 with an architecture page coming soon? I'm really having a hard time gauging the maturity of software & services these days.
This website behaves very strangely... scroll hijack. Also everything is suuuuuper stretched out.
If you scroll down enough, you can't scroll up anymore!<p>EDIT: If you scroll down to the commit graph and have your mouse inside the big commit graph rectangle, you can't scroll up anymore!
Kudos. We did/built something internally to solve similar-ish problems <a href="https://www.shayon.dev/post/2026/283/versioned-filesystem-for-disposable-sandboxes/" rel="nofollow">https://www.shayon.dev/post/2026/283/versioned-filesystem-fo...</a>
The evergreen observation; The most self-promote-y among us are mostly using AI to reinvent solutions and disguise them as new designs. These address solved problems, which are themselves disguised as new <i>agentic</i> problems.<p>Celebrating and promoting this stuff does not help us get better at discovering and building <i>actually</i> new things; change my mind.
UnionFS and overlay2, and the concept of layer filesystems existing makes this naming unfortunate and confusing.
We went from copy/paste this | sudo bash --> Copy this large prompt that installs stuff | AI Agent
~245k lines of Rust the LLMs coded. So my question is other than DSH does the author(s) have any advice on setup that made creating this possible? or other have tips for best setup that can produce a project like this.<p>Even those bashing for being AI generated have to admit it’s technically impressive and reflective of where software engineering is headed.
Nice website, but that's about it
I have to try it but I am very well interested in the decentralized agents mentioned there, I am tired of scattered agents and sessions across multiple OSes and harnesses I have, I just need one say an LXC that I can self host and automatically sync (or rather async like push/pull) all my harnesses, regardless wherever the previous session was.
How is this any different than something like btrfs?
It is more content aware and tuned towards versioned data vs block aware among other things. There’s a benchmark as to how it impacts things in the site<p><a href="https://layerfs.ai/benchmarks/dsh-dedup/" rel="nofollow">https://layerfs.ai/benchmarks/dsh-dedup/</a><p>I think it’s actually a fairly useful thing but I worry about something so obviously vibe coded hitting 1.0.0 and without a track record but the ideas seem pretty useful. I’ve certainly found the work tree semantics most agents and harnesses follow at scale to be obnoxious at best and it seems to tackle issues head on.
Nice benchmarks, impressive numbers. 20x less space than btrfs for the deep seek harness.<p>They even have some explanations. Files writes in btrfs snapshots recreatethe contents as opposed to storing what's changed. Btrfs has no dedupe, if multiple snapshots happen to have the same data. And small files store metadata twice in btrfs for reasons.<p>I do think their use case is a bit pathological, checking out the same harness at every commit. Most of these btrfs gotchas don't feel like they would be super impactful to me. But really cool results none the less.
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.<p>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.
"btrfs is battle tested"<p>Only in a sense that i went to a battle and lost all of its data to corruption. Should be removed from in-tree so people don't accidently use it.
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<p>And still crashes and corrupts filesystems all the time.<p>(I have one server platform where just doing `insmod btrfs` immediately locks up the server, hard, without even any kernel panic or log message.)
Or this
<a href="https://arxiv.org/html/2602.08199v1" rel="nofollow">https://arxiv.org/html/2602.08199v1</a>
ho yes please hack my browser scroll so I can't read your site (MacOS Safari)
[flagged]
[flagged]
[flagged]
[flagged]
[flagged]
[dead]