Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There was a great article about the common misconceptions about REST recently: https://twobithistory.org/2020/06/28/rest.html

The longer I think about it, the more I come to the conclusion that REST is simply not useful for application development in general. It is no accident that most APIs called "RESTful" by their creators are violating basic REST principles. But REST has some useful attributes even if not used strictly - caching comes to mind.

The question is: should we have another "standard" for web application development? Something more like RPC? There are some approaches, but nothing that I would call a broadly accepted standard. How should such a standard look like?



Yes we should. We should have a standard which is actually a standard and actually makes sense for what people are actually writing APIs to do.

gRPC would be a candidate, but the need for dev-side tooling to turn proto files into code is a bit of a downer.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: