E.g. store.users('bob').delete() and GET api.<domain>.com/users/bob/delete translates well I reckon
I'm actually more and more convinced REST API's are bad. RPC is the way to go. Function calls are what we do so why not be consistent?
-
-
-
People generally prefer SDKs and I think for good reason: they reflect how we reason about stuff. The whole REST thing feels like a dogma
- 5 more replies
New conversation -
-
-
REST makes more sense for PUBLIC APIs, IMO... but private? ehhhhh
-
why does it make sense for public APIs? All popular APIs ship SDKs anyway so why not optimize for simplicity?
End of conversation
New conversation -
-
-
because rest APIs give you 'free' api expectations through convention
-
yeah but they're horrible. Nobody's making sense of this stuff and everyone tries but then like it's still bad
End of conversation
New conversation -
-
-
until it is stateful
-
hah, but then people use Redux which is basically RPC and seem to do fine for mutating state. Idk, I'm missing arguments fór REST
- 1 more reply
New conversation -
-
-
I think REST without Hypermedia is basically pointless, the client has to know way too much.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
connection management + server/client data types differences may have influenced REST popularity. Both issues r easy with node
-
keeping connections alive was expensive for most backend stacks. RPC feels much more natural but there are few examples/pattrns
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.