Top all-time · #6733
Arnaud Lauret
Personal blog · apihandyman.iowebprogrammingcareer
Arnaud Lauret writes API Handyman, a personal blog at apihandyman.io about web, programming and career. Since 2015, 12 different Hacker News readers have linked it 16 times, most often “Do you really know why you prefer REST over RPC?”. The last post was in 2022, but the archive is still widely read.
Too few sampled comments (4) to say how often HN recommends it.?
Why HN links it
HN readers link Arnaud Lauret's API posts, mainly his jq tutorial for working with OpenAPI specs, which one commenter calls the most useful tutorial for that. Another calls a Swagger tutorial fantastic.
Summarised by Claude from a sample of 4 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Hi! I'm Arnaud Lauret, the API Handyman and author of The Design of Web APIs. I like to share what I do, struggle with, learn, and teach while working in the API space.
Most-linked posts?
- Do you really know why you prefer REST over RPC?3 people · 3 mentions · first linked 2017-03-22
- Do you really know why you prefer REST over RPC?2 people · 2 mentions · first linked 2015-05-11
What Hacker News says?
The full link: https://apihandyman.io/api-toolbox-jq-and-openapi-part-1-usi...
Comment linking /api-toolbox-jq-and-openapi-part-1-using-jq-to-extract-data-from-openapi-files/
on “An Introduction to JQ”Submitted Do you really know why you prefer REST over RPC? as a story · 111 points
HN discussionMy OpenAPI spec is 60,000 lines of machine generated goodness. JQ is great for doing non-trivial but useful things. Eg: Which endpoints are available if you have a specific OAuth Scope? Most useful jq cli flag is -f. - take the jq script from file Most useful tutorial for learning to manipulated your OpenAPI spec https://apihandyman.io/api-toolbox-jq-and-openapi-part-1-usi ...
Comment linking /api-toolbox-jq-and-openapi-part-1-usi
on “An Introduction to JQ”Submitted And GraphQL for all? A few things to think about before blindly dumping REST as a story · 3 points
HN discussionIt is amazing to me that almost nobody here actually questioned the wisdom of throwing out the time tested benefits of robustness of REST in exchange for that which REST was created to eliminate; the fragility of RPC. And all because using RPC is easier in the moment (vs. over time.) This reminds of of the old saw "Those who ignore history are doomed to repeat it." If you are unaware of the benefits, here are a just…
Comment linking /do-you-really-know-why-you-prefer-rest-over-rpc/
on “Twirp: A new RPC framework for Go”Submitted Do you really know why you prefer REST over RPC? as a story · 3 points
HN discussionWhich editor do you use to edit Swagger? Writing Swagger specification by hand is a nightmare because of the poor online editor. The error messages are hard to understand. Also Swagger.io people decided to replace the old editor with the new editor and it doesn't have many useful features the old has. Thankfully they kept the old one live. Swagger is not all that hard to understand. This is a fantastic tutorial whic…
Comment linking /writing-openapi-swagger-specification-tutorial-part-1-introduction/
on “Swagger is now the OpenAPI Specification”Submitted Automate all the things with GitHub actions, Postman and APIs as a story · 2 points
HN discussionSubmitted HTTP status code 401 vs. 403 vs. 404 as a story · 2 points
HN discussionSubmitted Adopt and not assess OpenAPI linters in the Thoughtworks Radar as a story · 2 points
HN discussionSubmitted Do you really know why you prefer REST over RPC? as a story · 2 points
HN discussionSubmitted Do you really know why you prefer REST over RPC? as a story · 2 points
HN discussionSubmitted Empty list: HTTP status code 200 vs. 204 vs. 404 as a story · 1 points
HN discussionSubmitted 404 vs. 405 vs. 501 as a story · 1 points
HN discussionSubmitted Do you really know why you prefer REST over RPC as a story · 1 points
HN discussionSubmitted The beautiful API and the bestial back office, a comic as a story · 1 points
HN discussion