[YellowRex]

I just wrote a REST API for my company and used PUT and DELETE (Tomcat doesn't support PATCH yet).

Plenty of DELETE in Stripe's API: https://stripe.com/docs/api#delete_recipient

Github uses HEAD, PATCH, PUT, and DELETE: http://developer.github.com/v3/#http-verbs

Twilio supports PUT and DELETE: http://www.twilio.com/docs/api/rest/request

There are all darlings of the HK community with highly praised, widely used REST APIs. Have you read through the developer docs for most APIs?

(edit: typo)

[ramchip]

To be fair to the other poster, I wouldn't be surprised if 99.9% of requests were GET/POST/HEAD.

[Gigablah]

And 99.9% of requests are GET rather than POST, so shall we get rid of POST then?

[shawnz]

GET and POST already have widely observed distinctions in how they should be handled. For example, try hitting refresh on a page that was arrived at via a POST request. That behaviour is pretty much common to all browsers.

[tericho]

His point was that at minimum you still need a GET and POST for read and write. So comparing the numbers against bike-shed implementations is moot. Of course the number of reads will be significantly higher.

[icebraining]

You could write and read using just POST. SOAP is the living example of that. So I think his point is inconsistent.