News for hackers. Stuff that matters.
Re:Stop Writing REST API Clients by TelmoMenezes on Sunday February 24, 2013 @11:16AM (#5274692)
Am I the only one who doesn't like receiving direct orders from article titles?
Re:Stop Writing REST API Clients by edanm on Sunday February 24, 2013 @11:45AM (#5274812)
Writing using authoritative language is very common, and widely considered a best practice.

I highly recommend you simply accept it as what it is: the way some people communicate, especially online. It's not worth your time/attention/care to think about this.

Re:Stop Writing REST API Clients by raverbashing on Sunday February 24, 2013 @11:47AM (#5274825)
Yes, you're right

But it still looks like they pulled some rules out of nowhere and are enforcing them.

Re:Stop Writing REST API Clients by pifflesnort on Sunday February 24, 2013 @04:58PM (#5276091)
Writing 'authoritatively' is used as a pop-culture substitute for reasoned argument. I find that it's a good litmus test for determining who I should ignore.
Re:Stop Writing REST API Clients by TallboyOne on Sunday February 24, 2013 @11:36AM (#5274780)
I was just thinking that, I hate article titles that are phrased exactly as a command and it's merely a blog post that wants to change an entire body of thought that's well founded.
Re:Stop Writing REST API Clients by steve918 on Sunday February 24, 2013 @01:05PM (#5275162)
I take all direct orders as suggestions. Sometimes this gets me into trouble; The same way it does my 2 year old. Most of the time though, it's the way to go.
Re:Stop Writing REST API Clients by INTPenis on Sunday February 24, 2013 @01:59PM (#5275387)
No, I got quite mad when I read the whole promotional article for his new node.js program without seeing a single argument against REST APIs.
Re:Stop Writing REST API Clients by readme on Sunday February 24, 2013 @02:16PM (#5275468)
That's because the article does not argue against REST APIs. It argues against coding wrappers for them and instead proposes a solution that allows you to define API specific behavior in JSON and use one library to rule them all.
Re:Stop Writing REST API Clients by shurcooL on Sunday February 24, 2013 @11:33AM (#5274763)
Would it help if he prefixed it with "In this article, I argue for why I believe that you should"?
Re:Stop Writing REST API Clients by ansgri on Sunday February 24, 2013 @12:06PM (#5274903)
"A way to stop reinventing REST API clients."
Re:Stop Writing REST API Clients by mattdeboard on Sunday February 24, 2013 @11:39AM (#5274789)
Yes. Assuming guru voice just makes you sound like a blowhard.
Re:Stop Writing REST API Clients by shurcooL on Sunday February 24, 2013 @11:49AM (#5274840)
Personally, I just assume that implicitly.
Re:Stop Writing REST API Clients by Goranek on Sunday February 24, 2013 @11:39AM (#5274791)
Yes! :)
Re:Stop Writing REST API Clients by Goopplesoft on Sunday February 24, 2013 @11:35AM (#5274776)
I was thinking about this yesterday, but its seems like HN likes that kinda thing. Lots of frontpage article are direct orders from blogs with who knows what credibility.
Re:Stop Writing REST API Clients by ubermammal on Saturday March 02, 2013 @12:44PM (#5310264)
You aren't, but it's a mistaken thing to dislike: there's no value to rephrasing it as "I believe you should [do X]" or "I am arguing that you should [do X]" because that's necessarily always true anyway, i.e. no article can ever be anything other than what the author believes and argues for. So 'softening' the language would be inefficient - it would use more words while adding nothing of substance.
Re:Stop Writing REST API Clients by jasonkostempski on Sunday February 24, 2013 @12:42PM (#5275070)
I read it as (I'd like to show you something that may help you) "Stop writing REST API clients". Imagine trying to visually scan HN article titles having to filter through useless pleasantries like that.
Re:Stop Writing REST API Clients by onlyup on Sunday February 24, 2013 @11:47AM (#5274827)
It irritates me too.
Re:Stop Writing REST API Clients by njy on Sunday February 24, 2013 @11:47AM (#5274824)
Try reading that with the voice of Morgan Freeman. Now THAT is something you would likely do :)