For decades, the RPC abstraction has been known to be fraught with serious problems related to partial failure, latency, and concurrency. Still, many developers continue to use RPC—some are even developing and open-sourcing new RPC systems—all in the name of convenience. Given all the known problems that plague RPC, and given better alternatives such as REST, should today's distributed systems developers really be choosing convenience over correctness?