Hacker News new | ask | show | jobs
by jkhdigital 1673 days ago
Classic example of a leaky abstraction, and the principle that implementation details inevitably become undocumented API behavior.
2 comments

A 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 . . .
I’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.