24 ms·
Hm this was the predominant way things were done about 10 years ago, and I think many people decided it ended up being harder to read. Take this to its logical
by whoisthemachine 12y ago
Hm this was the predominant way things were done about 10 years ago, and I think many people decided it ended up being harder to read.
Take this to its logical conclusion, and you end up with "http://mywebsite/getUserProfileFirstAddress" http://mywebsite/getUserProfileFirstAddress" when you want an endpoint that just returns the first address (or you end up with lots of stuff in a query string that ends up becoming a quasi-programming language), as opposed to a "restful" way of doing it, "user/1/profile/address/1". It's not so much about being readable for computers, we can solve that problem, it's about being readable for humans, which is the harder problem to solve.
- MichaelGG 12y agoBut REST is not about human readable APIs at all! You're supposed to get those URLs via hypermedia, right? Your comment is great though. That's all people really want when they say REST (most people, anyways). It's codeword for "please don't use SOAP or otherwise make your API extra hard to use".
- whoisthemachine 12y agoHa yeah sheesh hypermedia... can I get a hypercard over that? Anecdotally though - I find "restful" APIs much easier to parse and comprehend by eye than the old SOAP/Contract method.