(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| var parser = document.createElement('a'); | |
| parser.href = "http://example.com:3000/pathname/?search=test#hash"; | |
| parser.protocol; // => "http:" | |
| parser.hostname; // => "example.com" | |
| parser.port; // => "3000" | |
| parser.pathname; // => "/pathname/" | |
| parser.search; // => "?search=test" | |
| parser.hash; // => "#hash" | |
| parser.host; // => "example.com:3000" | 
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
| var gulp = require('gulp'), | |
| q = require('q'), | |
| path = require('path'), | |
| fs = require('fs'), | |
| Grunticon = require('grunticon-lib'); | |
| gulp.task('icons', function () { | |
| var deferred = q.defer(), | |
| iconDir = 'app/images/icons/', | |
| options = { enhanceSVG: true }; | 
A non-exhaustive list of flux and flux-like libraries with relevant information and notes.
| Library | Stars | Latest Release | 
|---|---|---|
| Facebook flux | ||
| reflux | ||
| fluxxor | ||
| marty | [ | 
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.
At the moment GraphQL allows 2 types of queries:
querymutationReference 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.
| if (typeof Promise === 'undefined') { | |
| require.ensure([], (require) => { | |
| require('imports?this=>window!es6-promise') | |
| }) | |
| } | |
| if (typeof fetch === 'undefined') { | |
| require.ensure([], (require) => { | |
| require('imports?self=>window!whatwg-fetch') | |
| }) | 
| 'use strict'; | |
| import React, { | |
| AppRegistry, | |
| Component, | |
| StyleSheet, | |
| Text, | |
| View, | |
| TouchableOpacity, | |
| LayoutAnimation, | |
| } from 'react-native'; | 
I've designed a lot of RPC protocols in my career. One pattern that's worked well basically goes as follows:
// Client calls: print('Hello World\n')
-> [1, "print", "Hello World!\n"]
// Server sends return value (or lack of return vvalue)
<- [-1]
// Client calls: add(1, 2)
-> [2, "add", 1, 2]