Updates to Facebook’s GraphQL License

What it is and Why it matters

GraphQL Patent Analysis breaks down the revisions Facebook has given to its GraphQL license terms. The author explains why this is an issue far from resolved. At least REST is not subject to licensing restrictions.

GraphQL

GraphQL is sometimes presented as the REST killer. Instead of pulling down large collections of data and having multiple moments of processing–such as querying  a BookTable and an AuthorTable–in lieu of calling a single function that will make the decision of how to make the calls for the individual data sources.

Getting Started with GraphQL provides a quick intro, although its usage of rather dated syntax, such as var instead of const or let, and require rather than import, distract from its presentation as the post-rest solution in an sql-free world.

Promise to Await Async

If you are still using promises and avoiding its replacement, this article on Six Reasons to Await/Async instead of Promise gives good reasons to move forward in asynchronous JavaScript. It is old news that current frameworks transpile before devices and browsers ever see the code we author. With that in mind, why would we not write the cleanest code we can while keeping our eyes on the near-term horizon of JavaScript functionality. Although the article references await/async support in node 7.6+, the reality is babel and typescript each have their own ways of processing await/async functions that may involve generators, modules and old-fashioned promises in their compiled output.

Why should we fix something not yet broken? While users of pug may be jaded, and users of coffeescript see its features becoming native in one framework after the next, the attraction to await/async is that it is almost universally embraced and expected to grow in usage due to its conciseness. One could argue that transpiling await/async can create a degree of code bloat, its terseness and existing or coming inclusion in all major browsers should moot that argument.

If you currently transpile your code, replacing promises is something you can begin today without breaking anything. That said, check out a new branch just to make sure!

The AR Wars have begun

Apple’s ARKit and Google’s ARCore are going head to head in the new battlefield named AR. Augmented Reality brings VR ornamentation to the otherwise dull analog lives that we all enjoy. One sad comment to notice at the outset is that the two systems are incompatible. The world is still waiting for a killer app that does not involve people running into trees looking for Pokemon treats.

Mashable gives first round to Apple