3 ms·
> So why on earth would you use that very bad library design Because when you design a Web API you're not designing a library, you're designing part of a distr
by bct 13y ago
> So why on earth would you use that very bad library design
Because when you design a Web API you're not designing a library, you're designing part of a distributed system.
Accessing code on a remote server is not like accessing code in a DLL, and never will be.
- mattmanser 13y agoThat was just an example. It's a computer asking for an action talking to a computer asking for an action. Call them whatever you want, the concept is extremely simple and pretending it's anything more complicated is obfuscating the underlying simplicity of the intent of the programmer. i.e. I want the other computer to do something or the other computer to send this computer some information.
- bct 13y agoThe intent is simple, but there are many ways to express that intent. Some of them work well when there are two components sitting right next to each other in memory on one machine; others work well for an unknown number of components interacting with each other over a slow, unreliable network. Even if RPC is a fundamentally, unambiguously simpler way to express that intent (and I think that's arguable), it does not meet the same technical requirements that REST does.