Räghib Hasan ragmha

In this gist I would like to describe an idea for GraphQL subscriptions. It was inspired by conversations about subscriptions in the GraphQL slack channel and different GH issues, like #89 and #411.

Conceptual Model

At the moment GraphQL allows 2 types of queries:

query
mutation

Reference implementation also adds the third type: subscription. It does not have any semantics yet, so here I would like to propose one possible semantics interpretation and the reasoning behind it.

Host react application on Apache server

Step 1 : Create your app

$ npm install -g create-react-app 
$ create-react-app my-app

Step 2 : Build it for production

How we incorporate next and cloudfront (2018-04-21)

Feel free to contact me at [email protected] or tweet at me @statisticsftw

This is a rough outline of how we utilize next.js and S3/Cloudfront. Hope it helps!

It assumes some knowledge of AWS.

Goals

Starving the Event Loop with microtasks

"What's the Event Loop?"

Sparked from this twitter conversation when talking about doing fast async rendering of declarative UIs in Preact

These examples show how it's possible to starve the main event loop with microtasks (because the microtask queue is emptied at the end of every item in the event loop queue). Note that these are contrived examples, but can be reflective of situations where Promises are incorrectly expected to yield to the event loop "because they're async".

setTimeout-only.js is there to form a baseline

state-machine-component

A tiny (265 byte) utility to create state machine components using two pure functions.

🔥 JSFiddle Demo

Usage

The API is a single function that accepts 2 pure functions as arguments:

Terminology

View: Also called a "template", a file that contains markup (like HTML) and optionally additional instructions on how to generate snippets of HTML, such as text interpolation, loops, conditionals, includes, and so on.
View engine: Also called a "template library" or "templater", ie. a library that implements view functionality, and potentially also a custom language for specifying it (like Pug does).
HTML templater: A template library that's designed specifically for generating HTML. It understands document structure and thus can provide useful advanced tools like mixins, as well as more secure output escaping (since it can determine the right escaping approach from the context in which a value is used), but it also means that the templater is not useful for anything other than HTML.
String-based templater: A template library that implements templating logic, but that has no understanding of the content it is generating - it simply concatenates together strings, potenti

Knowledge Base

If I had to start over, that's the list I'd follow...

	import React from 'react'
	import { BrowserRouter as Router, Switch } from 'react-router-dom'
	import routes from './routes'
	import FancyRoute from './components/tools/FancyRoute'

	const App = props =>
	<Router>
	<Switch>
	{routes.map((route, i) =>
	<FancyRoute key={i} {...route} />

	import webpack from 'webpack';
	import { resolve } from 'path';
	import HtmlWebpackPlugin from 'html-webpack-plugin';
	import ProgressBarPlugin from 'progress-bar-webpack-plugin';
	import ExtractTextPlugin from 'extract-text-webpack-plugin';
	import CopyWebpackPlugin from 'copy-webpack-plugin';
	import combineLoaders from 'webpack-combine-loaders';
	import { getIfUtils, removeEmpty } from 'webpack-config-utils';
	import autoprefixer from 'autoprefixer';