Yaron Naveh yaronn

Navigation and Resource Timing provides timing data for the fetch, but currently there is no interoperable way for the server to communicate own timing information to the client. For example:

What steps were taken to generate the resource, and how long each took. Many sites already embed this type of information via HTML comments - e.g. wordpress emits  , and many sites provide more detailed stats (cache, db, generation) to enable performance debugging.
If proxied, where was the time spent - e.g. time to fetch from origin, time to process response, etc.

Instead of relying on arbitrary HTML comments, we can define an HTTP header that can be used to send key-value pairs in a well defined format. Making this data available via a well defined interface would...

Allow UA and other developer tools to automatically annotate appropriate timelines.
Allow analytics vendors to gather this data for operational analysis.
Allows proxies and CDNs to append custom timing d

The final result: require() any module on npm in your browser console with browserify

This article is written to explain how the above gif works in the chrome (and other) browser consoles. A quick disclaimer: this whole thing is a huge hack, it shouldn't be used for anything seriously, and there are probably much better ways of accomplishing the same.

Update: There are much better ways of accomplishing the same, and the script has been updated to use a much simpler method pulling directly from browserify-cdn. See this thread for details: mathisonian/requirify#5

inspiration

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

tmux cheat sheet

(C-x means ctrl+x, M-x means alt+x)

Prefix key

The default prefix is C-b. If you (or your muscle memory) prefer C-a, you need to add this to ~/.tmux.conf:

remap prefix to Control + a

	Hi,

	Thanks for your mail, since you're one of many people asking this
	here are the facts about me not having released an update yet:

	- I'm aware of the upstream release and the breakage of my software
	- I'm working on software like the one you asked about in my spare time
	- I have limited spare time since I'm just one person
	- I've spent extensive time on the software (see master branch)
	but my limited sparetime still ran out eventually

	package main

	import (
	"fmt"
	"github.com/nfnt/resize"
	"image"
	"image/color"
	_ "image/gif"
	_ "image/jpeg"
	_ "image/png"

	/** @jsx React.DOM */

	var App = React.createClass({
	getInitialState: function() {
	return {
	pageSize: 2
	}
	}

	, render: function() {

	var http = require('http');

	http.createServer(function (request, response) {
	response.setHeader('Content-Type', 'text/html; charset=UTF-8');
	response.setHeader('Transfer-Encoding', 'chunked');

	var html =
	'<!DOCTYPE html>' +
	'<html lang="en">' +
	'<head>' +

	/*
	WorkCrew - a WebWorker work queue library

	Usage:

	// Create an 8 worker pool using worker.js.
	var crew = new WorkCrew('worker.js', 8);

	// Do something whenever a job is completed.
	// The result object structure is

	#!/usr/bin/env python
	# Reflects the requests from HTTP methods GET, POST, PUT, and DELETE
	# Written by Nathan Hamiel (2010)

	from BaseHTTPServer import HTTPServer, BaseHTTPRequestHandler
	from optparse import OptionParser

	class RequestHandler(BaseHTTPRequestHandler):

	def do_GET(self):