2 ms·
Applications are usually written to know that anything sent over the network could be lost. You don't usually do the same for sending to the different devices.
by taeric 3y ago
Applications are usually written to know that anything sent over the network could be lost. You don't usually do the same for sending to the different devices. Are you expecting retry logic in all places sending to a device?
We /could/ turn all computation into remote procedure calls. There is plenty of precedence that that will not end well. You do it where you have to. Not everywhere.
And fair point on the device learning its "off" position at startup. Though, that really leans into another point I made in another branch. That level of "isolated and can restart" is already largely accomplished by having extra compute on the devices you are connecting to. I really can't see much benefit it doing everything in the RPC paradigm.
I get the promise. I'm not buying the evidence that you can solve this by making it transparent that all things are "servers" and some are remote.
- klodolph 3y ago> Applications are usually written to know that anything sent over the network could be lost. Generally they are—when you make an HTTP request, the client waits until it receives an HTTP response before it reports success. > We /could/ turn all computation into remote procedure calls. There is plenty of precedence that that will not end well. You do it where you have to. Not everywhere. I think you may be having some kind of a different conversation here. I don’t understand your position, and I don’t think you understand mine.
- taeric 3y agoMicrokernels treating every system in the machine as a "service" is literally asking developers to treat everything as a distributed system. No? Was literally a selling point early on in the literature for them. There are good arguments for this in some environments.