Zeeshan Rasool zshnr

Data Down / Actions Up
- http://emberjs.jsbin.com/nayaho/edit?html,js - Interdependent select boxes. No observers.
- http://ember-twiddle.com/2d7246875098d0dbb4a4 - One Way Input
Plain JSBin's
- http://rwjblue.jsbin.com/pixeki/edit?html,js,output
Ember Version Base JSBin's
- 1.0 - http://emberjs.jsbin.com/juluje/edit?html,js,output
1.1 - http://emberjs.jsbin.com/cofufo/edit?html,js,output

The introduction to Reactive Programming you've been missing

This tutorial as a series of videos

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.

Parens And Performance

Years ago, some smart folks that worked on JS engines realized that not all JS that's loaded into a page/app initially is needed right away. They implemented JIT to optimize this situation.

JIT means Just-In-Time, which means essentially that the engine can defer processing (parsing, compiling) certain parts of a JS program until a later time, for example when the function in question is actually needed. This deferral means the engine is freer to spend the important cycles right now on the code that's going to run right now. This is a really good thing for JS performance.

Some time later, some JS engine devs realized that they needed to get some hints from the code as to which functions would run right away, and which ones wouldn't. In technical speak, these hints are called heuristics.

So they realized that one very common pattern for knowing that a function was going to run right away is if the first character before the function keyword was a (, because that usually m

How to use:

./wordle.sh

Or try the unlimit mode:

	/*
	You want to use webworkers, but you host all of your js files on a different domain than where
	your app lives (es. app.example.com and js.example.com). Given that the static file served from
	js.example.com are CORS ready (in that the response header includes Accept-origin: *), I thought
	I could load a Worker from other domains. I was almost wrong, but at last I found a solution:
	XHRing the worker source and create an inline worker. This is tested only on Firefox (latest).
	*/
	// This is an example webworker that is on js.example.com. It just echoes messages it receive.
	self.onmessage = function(e) {
	self.postMessage(e.data);

	function asyncThread(fn, ...args) {
	if (!window.Worker) throw Promise.reject(
	new ReferenceError(`WebWorkers aren't available.`)
	);

	const fnWorker = `
	self.onmessage = function(message) {
	(${fn.toString()})
	.apply(null, message.data)
	.then(result => self.postMessage(result));

	# vid: https://vimeo.com/248529140
	# tweetable versions:
	# https://twitter.com/josh_cheek/status/1013189676008722433
	# https://twitter.com/josh_cheek/status/1013182568307535873
	ruby -r io/console -e '
	h, w = $stdin.winsize
	time = []
	def time.[](i)
	super \|\| (
	moment = {green: [], white: [], off: []}