Hacker News Reader

Comment by mehrdadn | Hacker News Reader

Not sure if I'm being naive, but couldn't they make it so that if there are no filters present on a given volume, then the entire filter stack is bypassed and the directory nodes are served from a cache managed by the file system at the root of the volume? That way developers who really want performance can make sure they have no filter drivers installed on that volume.

View on HN

The linked post notes that, even on a default Windows install, you already have a sizable stack of filter drivers active. Not sure whether that only applies to the C: volume or to other ones as well.

If they really wanted to, they could mount an ext4 fs as a single blob on disk directly into WSL. That won't really help if you want to run a GUI editor in windows against that identical directory though.

Any idea why they haven't responded to people's requests for FUSE? It's the second-most requested feature and should enable applications like this.

They have: https://docs.microsoft.com/en-us/windows/desktop/projfs/proj...

That looks awesome (thanks for sharing) but it seems to be a different thing? People are looking for a way to run existing Linux FUSE in SL, not develop new virtual file system implementations. They haven't responded to that request at all. https://wpdev.uservoice.com/forums/266908-command-prompt-con...

Windows expects different things from an FS, so it makes sense for a native userspace FS API to be different from FUSE.

But once you have it, it shouldn't be difficult to write a FUSE adapter on top, mapping across those differences as best as possible.

Reply on news.ycombinator.com