> Our multiplayer filesystem persists its data to Durable Objects with the help of DOFS - a mostly POSIX compatible filesystem layer with Emscripten's filesystem interface.
This reminds me of HAFS – a FUSE-based filesystem based on FoundationDB [1]. It does a lot of the same things under the hood to work with FDB's requirements (i.e. slicing, etc). Looking forward to seeing your time travel implementation.
Regarding Gitlip – I've spent a lot of time in the gaming industry where many workflows rely on Perforce for collaboration/file locking instead of Git & Git LFS. It's a widely disdained tool because of its rigidity and complexity. Gitlip feels like a better approach to collaboration than Perforce, but applied to wider use cases. I'll have to give it a spin some time.
This reminds me of HAFS – a FUSE-based filesystem based on FoundationDB [1]. It does a lot of the same things under the hood to work with FDB's requirements (i.e. slicing, etc). Looking forward to seeing your time travel implementation.
Regarding Gitlip – I've spent a lot of time in the gaming industry where many workflows rely on Perforce for collaboration/file locking instead of Git & Git LFS. It's a widely disdained tool because of its rigidity and complexity. Gitlip feels like a better approach to collaboration than Perforce, but applied to wider use cases. I'll have to give it a spin some time.
[1] https://github.com/andrewchambers/hafs