2 ms·
> Use an rpc protocol to do all the talking to objects within the system which are exposed as files. At some point, you're just adding pointless layers of indi
by zozbot234 7y ago
> Use an rpc protocol to do all the talking to objects within the system which are exposed as files.
At some point, you're just adding pointless layers of indirection by doing this. NT tried this approach, and it is anything but "simple".
You can do many things quite naturally by interacting with bytestream-like or block-like objects that are exposed via some sort of hierarchical namespace ("files"), but this doesn't really cover everything. Some things may be better done, even in a script, by interacting with a "binary" that in turn just wraps a binary library exposing some kind of ABI.
- kjs3 7y agoI don't disagree, per se, but designing for the exception is also a good way to end up with a mess. You have to carefully measure the impact (performance, maintenance, developer impact, etc.) of every special case.