<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>rantanplan</author><text>&amp;gt; I&amp;#x27;ve been trying hard for years to find a reason to bother with PUT, but so far I&amp;#x27;ve found it not worth the effort.&lt;p&gt;And right there, at your final sentence, you basically described why REST has more or less failed.&lt;p&gt;GET and POST are useless for implementing a  complete application protocol. You&amp;#x27;d basically overload these http verbs to the point where you would implement your own protocol. And that&amp;#x27;s what most people do anyway. You choose to not use PUT, some other person chooses to not use PATCH or HEAD and I choose to curse vehemently every time I have to use someone&amp;#x27;s service.&lt;p&gt;REST is nothing but loosely connected guidelines that nobody uses in the same manner.</text><parent_chain><item><author>codr4life</author><text>I&amp;#x27;m going to have to call bullshit on that one. REST is one of the more successful strategies we&amp;#x27;ve come up with for connecting systems, this is just another case of letting perfect stand in the way of good enough. Using GET for non-destructive operations and POST for updates and deletes is a nice, portable compromise. I&amp;#x27;ve been trying hard for years to find a reason to bother with PUT, but so far I&amp;#x27;ve found it not worth the effort.</text></item></parent_chain></comment><story><title>Problems with RESTful APIs (2015)</title><url>https://mmikowski.github.io/the_lie/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>alganet</author><text>You don&amp;#x27;t need PUT nor DELETE. It is OK to use POST[1].&lt;p&gt;Most people don&amp;#x27;t understand REST. It is not a standard, it is not a set of practices. It is an architectural style and the web is built on it.&lt;p&gt;You can choose to follow the style (which is so much more than naming methods and URIs) or fight it. The dissertation is pretty clear about it[2], but most people ignore it because there are no code samples.&lt;p&gt;[1]: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;roy.gbiv.com&amp;#x2F;untangled&amp;#x2F;2009&amp;#x2F;it-is-okay-to-use-post&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;roy.gbiv.com&amp;#x2F;untangled&amp;#x2F;2009&amp;#x2F;it-is-okay-to-use-post&lt;/a&gt; (REST creator talking about the PUT misconception)&lt;p&gt;[2]: &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;www.ics.uci.edu&amp;#x2F;~fielding&amp;#x2F;pubs&amp;#x2F;dissertation&amp;#x2F;top.htm&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;www.ics.uci.edu&amp;#x2F;~fielding&amp;#x2F;pubs&amp;#x2F;dissertation&amp;#x2F;top.htm&lt;/a&gt; (Full REST dissertation)</text><parent_chain><item><author>codr4life</author><text>I&amp;#x27;m going to have to call bullshit on that one. REST is one of the more successful strategies we&amp;#x27;ve come up with for connecting systems, this is just another case of letting perfect stand in the way of good enough. Using GET for non-destructive operations and POST for updates and deletes is a nice, portable compromise. I&amp;#x27;ve been trying hard for years to find a reason to bother with PUT, but so far I&amp;#x27;ve found it not worth the effort.</text></item></parent_chain></comment><story><title>Problems with RESTful APIs (2015)</title><url>https://mmikowski.github.io/the_lie/</url></story>