I am a programmer so yes I can do this if I really really wanted to but right now I'm just daydreaming and looking for feedback on the idea.
One of the things I distaste is how programs dump their configuration files and directories in home. I'm thinking what if programs each had their own configurable virtual filesystem. They would observe remapped files and directories...
Take my favorite editor "joe" and it's .joerc file in the home directory. I could configure it so that only the program "joe" sees .joerc in my home directory but in actuality really it is in the ".config/joe directory". Likewise with all the other programs and their . files and directories.
It would be higher level of transparent symbolic linking/file rerouting. In fact it could act as a chroot mechanism and virtually remap everything to a directory just like chroot. But with the added benefit of all sort of other remapping. It could even do the equivalent of unionfs. But the difference would be that it would be acting at the "program view" level instead of the true filesystem level.
One of the things I distaste is how programs dump their configuration files and directories in home. I'm thinking what if programs each had their own configurable virtual filesystem. They would observe remapped files and directories...
Take my favorite editor "joe" and it's .joerc file in the home directory. I could configure it so that only the program "joe" sees .joerc in my home directory but in actuality really it is in the ".config/joe directory". Likewise with all the other programs and their . files and directories.
It would be higher level of transparent symbolic linking/file rerouting. In fact it could act as a chroot mechanism and virtually remap everything to a directory just like chroot. But with the added benefit of all sort of other remapping. It could even do the equivalent of unionfs. But the difference would be that it would be acting at the "program view" level instead of the true filesystem level.