Hacker News Reader

No HTTP PATCH support? Makes me a sad panda. PATCH > PUT.

It originally had PATCH in the design. I think it was a limitation of our tooling that made us reconsider. And that PUT was slightly more familiar for novice users. At the end of the day ... it doesn't matter. Either way is a huge improvement from all GET.

Totally agreed, but for us that also write and consume RESTful services, PATCH is the best way to prevent race conditions when you have multiple things updating at the same time. That and as a purist, I like the idea of updating the minimal amount vs the entire object all at once.

Regardless, this is a HUGE improvement, so nice work! Oh and please keep the interesting projects coming on github. I'm a fan of the docker + consul integration you've been working on.

I completely don't understand downvotes lately. Is it the joke? Or the use of a relation symbol instead of in-depth analysis of the pros and cons?

This is a legitim question that opens up a great topic about protocol support.

Reply on news.ycombinator.com