News for hackers. Stuff that matters.
Re:A set of best practices for JavaScript projects by sAbakumoff on Wednesday July 05, 2017 @06:58AM (#14701384)
> 9.2 Operating on resources

Sure, let's pretend that GraphQL is not a thing. Yep.

Re:A set of best practices for JavaScript projects by weego on Wednesday July 05, 2017 @07:04AM (#14701408)
Other than for a proverbial handful of people in the world, it isn't
Re:A set of best practices for JavaScript projects by sAbakumoff on Wednesday July 05, 2017 @07:09AM (#14701430)
I am a little bit more optimistic about it..I mean GitHub has recently introduced the GraphQL API..I guess that other SaaS's will follow - twitter, reddit, HN(or probably not) and so on.
Re:A set of best practices for JavaScript projects by always_good on Wednesday July 05, 2017 @01:22PM (#14704332)
Sarcasm is the laziest way to present an idea.

Why not just say what you mean?

Re:A set of best practices for JavaScript projects by sAbakumoff on Wednesday July 05, 2017 @04:02PM (#14705670)
On the other hand sarcasm is the gentlest way to criticize an idea :-)
Re:A set of best practices for JavaScript projects by vahidpg on Wednesday July 05, 2017 @09:59AM (#14702408)
We haven't developed anything with GraphQL yet. I wasn't even sure if there are best practices out there. If you have a link that lists them, I'd happily put it in the doc. You're more than welcome to make a pull request as well.