Presumably, if this were to catch on, it would start in toy projects and projects with a major usability advantage, where the performance loss is acceptable, an

Presumably, if this were to catch on, it would start in toy projects and projects with a major usability advantage, where the performance loss is acceptable, and as a secondary means of using other programs. Then, we might see optimizations to make the performance of this method not horrible. In concept, it should be relatively simple to recognize where a FUSE filesystem is mounting another FUSE filesystem and bypass the kernel to let the two processes talk directly to each other. You still have the problem that any operation would need to travel through N processes. You might be able to improve on this with a mechanism for a filesystem to say "I have to effect on operation X" and have it be bypassed when X occurs.