It’s a small attempt to model filesystem directories as reactive units rather than relying on ad-hoc file watching or polling.
The goal is to provide a consistent event-driven abstraction over folder changes that can be embedded into tooling or apps, instead of each project implementing its own filesystem watcher logic.
It’s still early, but the idea is to explore whether a more structured “reactive filesystem layer” is useful for things like dev tools, local-first apps, or build systems that respond directly to workspace changes.
Curious if this problem space is already well solved in other systems, or if people think the abstraction is useful at all.
I built and open sourced LiveFoldersFS:
https://www.livefoldersfs.org
It’s a small attempt to model filesystem directories as reactive units rather than relying on ad-hoc file watching or polling.
The goal is to provide a consistent event-driven abstraction over folder changes that can be embedded into tooling or apps, instead of each project implementing its own filesystem watcher logic.
It’s still early, but the idea is to explore whether a more structured “reactive filesystem layer” is useful for things like dev tools, local-first apps, or build systems that respond directly to workspace changes.
Curious if this problem space is already well solved in other systems, or if people think the abstraction is useful at all.