Lionel Tzatzkin elrumordelaluz

Fundamentals: why state machines?

States. The final frontier. These are the voyages of an enterprising developer. Her eternal mission: to explore strange new techniques, to seek out better ways to engineer for mental models and new design patterns. To boldly go where a few awesome devs have gone before.

So you’ve found our poignant guide to SCXML and surely you’re wondering “Why should I want to go out of my way to use formal state machines?” or something like that. Hopefully this introduction addresses that kind of question.

An example: Nancy’s RPG

The problem

Concept

People talk about two servers: a web server (e.g. Nginx, Apache, etc.) and a app server (e.g. Language specific servers like Unicorn, Node.js, Tomcat, Http-Kit, etc.). There are exceptions where app servers not required at all (as web server itself provides preprocessors for handling), but let's not talk about now.
Web servers are really fast and supports lot of standard and commonly used MIME-type requests. Concept of serving a file is -- forming and sending a response of bytes of data and labeling it with requested MIME-type by a client (e.g. web browser).
Every response format (in layman's language, a file) is recognized by it's MIME-type, for e.g. a PNG image file has "image/png" MIME-type. JavaScript file has "text/javascript". HTML responses (or files) has "text/html". Plain text files have "text/plain".
Modern Browsers supports a lot of standard MIME-types. Images, videos, text files (XML, HTML, SVG, JS), and they better know how to visualize it. Browser also knows unrec

I wanted to figure out the fastest way to load non-critical CSS so that the impact on initial page drawing is minimal.

TL;DR: Here's the solution I ended up with: https://github.com/filamentgroup/loadCSS/

For async JavaScript file requests, we have the async attribute to make this easy, but CSS file requests have no similar standard mechanism (at least, none that will still apply the CSS after loading - here are some async CSS loading conditions that do apply when CSS is inapplicable to media: https://gist.github.com/igrigorik/2935269#file-notes-md ).

Seems there are a couple ways to load and apply a CSS file in a non-blocking manner:

	// array utils
	// =================================================================================================

	const combine = (...arrays) => [].concat(...arrays);

	const compact = arr => arr.filter(Boolean);

	const contains = (() => Array.prototype.includes
	? (arr, value) => arr.includes(value)
	: (arr, value) => arr.some(el => el === value)

	http {

	map $http_user_agent $limit_bots {
	default '';
	~*(bing\|yandex\|msnbot) $binary_remote_addr;
	}

	limit_req_zone $limit_bots zone=bots:10m rate=1r/m;

	server {

	foo bar
	baz
	qux

	last line (there may or may not be a trailing newline after this line)

	// === Arrays

	var [a, b] = [1, 2];
	console.log(a, b);
	//=> 1 2


	// Use from functions, only select from pattern
	var foo = () => [1, 2, 3];

	<!doctype html>
	<html>
	<title>Flatten.js, General SVG Flattener</title>

	<head>
	<script>
	/*
	Random path and shape generator, flattener test base: https://jsfiddle.net/fjm9423q/embedded/result/
	Basic usage example: https://jsfiddle.net/nrjvmqur/embedded/result/

	// MultiExporter.jsx
	// Version 0.1
	// Version 0.2 Adds PNG and EPS exports
	// Version 0.3 Adds support for exporting at different resolutions
	// Version 0.4 Adds support for SVG, changed EPS behaviour to minimise output filesize
	// Version 0.5 Fixed cropping issues
	// Version 0.6 Added inner padding mode to prevent circular bounds clipping
	//
	// Copyright 2013 Tom Byrne
	// Comments or suggestions to tom@tbyrne.org