<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>shortrounddev2</author><text>I still like REST. Most web applications are CRUD and don&amp;#x27;t need RPC. It also provides a standard and expected interface for 3rd party developers integrating with your code. If you&amp;#x27;re a small saas startup, nobody is going to waste their time learning the particularities of your protocol. Also makes the code very easy to read if you follow best practices for MVC style webapis with dependency injection. In my view, asp.net core is the apex of all RESTful frameworks</text><parent_chain></parent_chain></comment><story><title>An Introduction to APIs</title><url>https://zapier.com/resources/guides/apis</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>dinoreic</author><text>REST is for noobs, JSON RPC is silent pro&amp;#x27;s choice :)&lt;p&gt;Make all requests POST and enjoy easy life without useless debates on should creation of resource be on POST or PUT or should you return HTTP status 404 or 200 if resource&amp;#x2F;document on server is not found (of course if should be 200 because request was a success, 404 should only be used it api method is not found).&lt;p&gt;I 100% agree with Troy Griffitts beautiful take &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;vmrcre.org&amp;#x2F;web&amp;#x2F;scribe&amp;#x2F;home&amp;#x2F;-&amp;#x2F;blogs&amp;#x2F;why-rest-sucks&quot; rel=&quot;nofollow noreferrer&quot;&gt;https:&amp;#x2F;&amp;#x2F;vmrcre.org&amp;#x2F;web&amp;#x2F;scribe&amp;#x2F;home&amp;#x2F;-&amp;#x2F;blogs&amp;#x2F;why-rest-sucks&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>An Introduction to APIs</title><url>https://zapier.com/resources/guides/apis</url></story>