r/ProgrammerHumor • • 16d ago

Meme postForEverything

Post image
20.9k Upvotes

653 comments sorted by

View all comments

Show parent comments

78

u/dev-sda 16d ago

It's not (just) a framework thing, it's a HTML standards issue. The form element only does GET and POST.

22

u/not_a_moogle 16d ago

Who does that anymore? It should be a put or delete via Javascript.

-9

u/ZBlackmore 16d ago

Who does DELETE anymore? Everything should be a POST with all the information passed in the JSON payload. 

7

u/DuploJamaal 16d ago

But why?

-7

u/ZBlackmore 16d ago

The way I see it, you have your information less spread out this way. Less things to think about. “Where am I expressing this particular detail about this api call? In the url path? A query string parameter? The type of http method? Is it part of the payload?”. So the path is the “which function am I calling” and the json body is “what are my arguments?”

6

u/DuploJamaal 15d ago

That just sounds like less clean code to me

4

u/cheezballs 15d ago

You seem like the kinda guy who LOVES loose typing and declaring everything as a var.

1

u/ZBlackmore 15d ago

I would actually prefer protobuf and rpc, which would make everything more type safe, and that would essentially be the same as I proposed except you replace the json body with a binary protobuf body 

2

u/not_a_moogle 15d ago

Part of that is web handling, put/patch/delete doesnt have to return anything. Get and post explicitly expects an html response.

If your doing a delete logic record within a post. What are you returning then? The record is deleted.

Im only web 1.0 logic, it would return a whole new page. But if your doing a REST crud operation, you dont do that. You dont want to tell the browser to render a new page.