Remix.run Logo
akurilin 2 days ago

This is great stuff, walking the reader through your thought process was helpful for me as a developer to grok why yolobox was designed this way. I ended up landing in the "just make a local copy, don't get fancy" world myself after many iterations of workflows. Separate agents, separate containers, separate ports, that all resonates.

You mention this approach gobbling up a bunch of extra disk space as a consequence of the tradeoffs. Have you considered using APFS cloning on macOS to reduce some of that burden, or is that too tiny of an optimization to be worth it at this point?

Finbarr 2 days ago | parent [-]

Hard drives are cheap and I haven't approached the limit yet. So I left this as a future optimization.

CodesInChaos 17 hours ago | parent [-]

I'd try a modern file system with de-duplication/copy-on-write support. `cp` creates reflinks automatically if the file-system supports copy-on-write.

> Support for reflinks is indicated using the remap_file_range operation, which is currently (6.18) supported by bcachefs, Btrfs, CIFS, NFS 4.2, OCFS2, overlayfs, and XFS. Some external file systems support them too, including bcachefs and OpenZFS.

https://unix.stackexchange.com/questions/631237/in-linux-whi...

Finbarr 15 hours ago | parent [-]

Interesting suggestion, thank you!