Re:Ask HN: At this point, are PUT and PATCH helpful?
by happytoexplain on Tuesday June 22, 2021 @12:18AM
(#27587951)
Usage of POST to update is so common, I don't think it's unreasonable to say it's a de-facto standard. Sort of like how if an English word/phrase is misused enough, the "wrong" version eventually makes it into dictionaries.
Re:Ask HN: At this point, are PUT and PATCH helpful?
by gls2ro on Tuesday June 22, 2021 @12:30AM
(#27588004)
This is the first time I hear that usage of POST to update is common.
Around me I cannot name one backend developer who will design an API with POST used for update. We did it in the past when browsers where not implementing PUT or PATCH but still sending method=PUT/PATCH as param.
Of course this is my experience and I might be in a bubble.
Re:Ask HN: At this point, are PUT and PATCH helpful?
by wvenable on Monday June 21, 2021 @11:56PM
(#27587824)
It doesn't really matter though.
If you misuse POST nobody and nothing is going to care. Literally every traditional web application, including this very site, "misuses" POST all the time.
Re:Ask HN: At this point, are PUT and PATCH helpful?
by seph-reed on Monday June 21, 2021 @10:45PM
(#27587381)
I often really like "anti-patterns."
They're usually a case of a ["desire path"](https://miro.medium.com/max/2592/0%2AD1R7QvewXmwUVytD.)
Typically, it says more to me about the designer than the users.
Yes, it matters. You're misusing POST in the first example.
C = POST R = GET U = PUT/PATCH D = DELETE
Doing anything else is an anti-pattern for interop on the web.