I wonder if we're doing virtual filesystems wrong.
There is a good reason why traditionally filesystem access was mediated by the OS layer, but there are many use cases where you just want to give processes a different view of what they already can access and it could be done as a library in the same userspace process.
However, for that to work across all the processes in a session we'd need a standard way to install such a hook in all peocesses and that's achievable to some extent using LD preload but falls apart quite rapidly with statically built binaries or different libcs
Sending -asScheme to a reference is just a shorthand that actually constructs a composition[2] of a "path relative" store with the underlying store of the original reference. So the following two are identical:
This composition mechanism can be carried further with post-processing, so for example an img-scheme can be constructed by composing an image-decoder store with the previous store
It's worse than that. No bank will have business with you because that would potentially affect _their_ other customer's ability to operate normally
This is a very big hammer and reveals how foreign entities are deeply dependent on the American financial system and thus exposed to the political whims of the US.
There are also consequences in letting Russia take Ukraine militarily.
Whatever you think about the motivations and the desired end goal, actions and lack of actions both have consequences
reply