> Finally, Plan 9 fits well with a networked environment. Since files
or directory trees can be imported from other machines, and all
resources are files or directory trees, it's easy to share resources.
Want to use a different machine's sound card? Import its /dev/audio.
Want to debug processes that run on another machine? Import its
/proc. Want to use a network interface on another machine? Import
its /net. And so on.
Does this kind of abstraction actually work well? Networks are generally quite unreliable so does it really work well to treat everything as files even when the latency can be so different depending on if the resource is local or remote? Do the plan9 APIs make it natural to write code that deals well with random blocking when reading/writing to files?
Does this kind of abstraction actually work well? Networks are generally quite unreliable so does it really work well to treat everything as files even when the latency can be so different depending on if the resource is local or remote? Do the plan9 APIs make it natural to write code that deals well with random blocking when reading/writing to files?