This is very clever. I know that if you are using this solution a lot for the same purpose (let's say rendering) then it would be beneficial to come up with a more efficient setup for your particular application.
But this could be very useful for ad hoc, or just spur of the moment things. Let's say I have a few servers that I have access to. Whenever I need to do something computation heavy and it could be something different everytime. Sometimes transcoding a video, sometimes compiling a library in rust. I just outsource them to the servers and keep using my laptop doing other stuff.
> a more efficient setup for your particular application
Yeah, once you get past ad hoc applications, one common way to set this up is to setup a cluster/batch scheduler. This lets your jobs be run on an available node. You don't get the same chroot/fuse filesystem voodoo, but once you have a cluster, then an NFS mount for applications is a common setup.
But this could be very useful for ad hoc, or just spur of the moment things. Let's say I have a few servers that I have access to. Whenever I need to do something computation heavy and it could be something different everytime. Sometimes transcoding a video, sometimes compiling a library in rust. I just outsource them to the servers and keep using my laptop doing other stuff.