3 ms·
> The goal of REST isn't to be the RPC protocol I'd politely disagree with that. I think most REST fanatics ACTUALLY DO claim that their beautiful arrangement
by WClayFerguson 6y ago
> The goal of REST isn't to be the RPC protocol
I'd politely disagree with that. I think most REST fanatics ACTUALLY DO claim that their beautiful arrangement of nouns and their 4 CRUD verbs are capable of replacing RPC, because they've become convinced the "procedure" part of RPC, means that RPC is inherently built around functional programming which is verbs, and they think they've found a better way than using a custom vocabulary of verbs.
So they're using REST instead of RPC, because "verbs are bad".
I'll just restate my opinion that the concepts of "functional programming" are not somehow rendered obsolete whenever the machine you're talking to happens to be remote. Sure, there are certain challenges involved with designing a 'remote' API that can arise involving latency and bandwidth considerations, but those limitations in no way imply a solution where you throw out your entire set of "verbs", like REST does.
- tsimionescu 6y agoI think that REST is the language of your API. Just like in a regular PL you normally have just a handful of verbs, as I said in my first answer, so to in REST you only need a few verbs. Of course, you then build up functionality over those base verbs, just like in a program. But your programming language doesn't have a verb for each function you might want to write. It just has the base 'call' verb.
- WClayFerguson 6y agoI've said everything I know to say, 10 different ways all over this thread. It's a topic lots of people have strong opinions about for sure.