5 ms·
Classic example of a leaky abstraction, and the principle that implementation details inevitably become undocumented API behavior.
by jkhdigital 5y ago
Classic example of a leaky abstraction, and the principle that implementation details inevitably become undocumented API behavior.
- kabdib 5y agoA lot of "transparent RPC" systems are like this. "It's just like a normal function call, it's sooo convenient" . . . until it isn't, because it involves the network hardware and configuration, routing environment, firewalls, equipment failure . . .
- andylynch 5y agoI’ve worked on systems like this too - the max packet size is very well documented. Then post trade it all gets turned into FIXML which somehow manages to be both more verbose and less readable.