booze

This is my favorite cursed finding: https://github.com/zevweiss/booze FUSE-bindings for "filesystems in bash", eg: https://github.com/zevweiss/booze/blob/master/cowsayfs.sh#L5... cs_read() { if ! [[ "$1" =~ ^/($cowpat)/[^/]+$ ]]; then booze_err=-$EINVAL return 1 elif [ "$3" != 0 ]; then return 0 fi local msg="${1#/*/}" local cow="${1#/}" cow="${cow%%/*}" cowsay -f "$cow" "$msg" } ...I think that WebDAV is "the way" compared to FUSE, but I'm always intrigued by the idea of virtual filesystems as an implementation face.

A good example for lulz is https://github.com/zevweiss/booze, a FUSE binding for bash. Aside: I've wondered aloud if we could figure out how to systemically compile coreutils into true bash builtins for performance benefits in nix builds, but someone did rightly point out that builtins can't be completely fungible with a separate process in all cases, especially where stuff like pipelines are involved. I don't recall the exact details and couldn't readily find the conversation but IIRC it had to do with signal handling. Edit: Found the conversation: https://gist.github.com/abathur/74e7a63b25b7bbd4a6fa9ad7e728...

I had forgotten completely about KDE + KIO Slaves. I've been on the lookout for a filesytem browser (eg: fuse/ssh-fs-ish, ratarmount, even this monstrosity: https://github.com/zevweiss/booze ), but had forgotten about the KDE file manager having support for "weird" protocol browsing!

Neat...and on a somewhat similar note (bash enable -f hacks), some bash FUSE bindings I wrote a few years back: https://github.com/zevweiss/booze I initially wrote it basically just for giggles, but was rather pleased a few months ago when I realized I could use it for something I actually needed, and it was just the right thing (presenting a mount point that acted as a view of the differences between two rsnapshot-style hard-link trees -- only took a few dozen lines of very simple code).