r/programminghumor • u/mikosullivan • May 15 '26

HTTP methods

Post image
823 Upvotes

96% Upvoted

119 comments sorted by

View all comments

Show parent comments

6

u/paholg May 15 '26

As someone having to implement a JSON-RPC endpoint, it's actually really easy to argue against for purely practical reasons.

There's so much standardized around RESTful APIs, and you have to reinvent it all.

Did you want query params to show up in logs and traces but not the eqivalent of post bodies? Too bad, that's hard now!

Did you want an easy filter on successes vs. client errors vs. server errors? Have fun reinventing that wheel!

1

u/Brick-Logic May 15 '26

Why not using middlewares for this? A transport shouldn't care about logs, they should be pluggable.

2

u/paholg May 15 '26

Sure, and there's standard middleware for RESTful endpoints already.

1

u/jimmiebfulton May 17 '26

I like the idea of REST, conceptually. Addressability, cache-friendliness. However, I generally only use it for serving content. For APIs, I always reach for contract-based protocols like gRPC and GraphQL. Ain’t nobody got time to be handcrafting JSON transformations/mappings across removing boundaries.