Comment by nimish
4 months ago
Neat! The "native" version of FUSE for windows is a "Shell Namespace Extension" and might make it a little more integrated.
https://learn.microsoft.com/en-us/windows/win32/shell/namesp...
4 months ago
Neat! The "native" version of FUSE for windows is a "Shell Namespace Extension" and might make it a little more integrated.
https://learn.microsoft.com/en-us/windows/win32/shell/namesp...
Thank you for the comment. The motivation for the development was the desire to easily view application logs in S3 (for free). Initially, I considered using FUSE, but I became interested after reading the following article: https://winfsp.dev/doc/Native-API-vs-FUSE/
Awesome, very interesting! Thanks for providing that.
WinFsp isn't "native" in the sense it's a wrapper on the Microsoft provided interface AFAICT
Shell Namespace extensions is the pure-windows way via COM and all that junk. WinFsp is very cool though since FUSE is a much nicer API but probably less you can do to be a very explorer thing
Thank you for the detailed explanation. Pure control of Explorer through COM also seems interesting. I'm still in the process of understanding WinFsp, so I can't get to that yet, but it's a challenge I want to tackle in the future.
1 reply →