Eyo O. Eyo eokoneyo

Problem: How can we preprocess JavaScript (at build-time or on the server-side) so engines like V8 don't have to spend as much time in Parse? This is a topic that involves generating either bytecode or a bytecode-like-abstraction that an engine would need to accept. For folks that don't know, modern web apps typically spend a lot longer in Parsing & Compiling JS than you may think.

Yoav: This can particularly be an issue on mobile. Same files getting parsed all the time for users. Theoretically if we moved the parsing work to the server-side, we would have to worry about it less.
One angle to this problem is we all ship too much JavaScript. That's one perspective. We could also look at preprocessing.
We've been talking about this topic over the last few weeks a bit with V8. There were three main options proposed.
1. Similar to what optimize-js does. Identify IIFEs and mark them as such so the browser and VMs heuristics will catch them and do a better job than today. optimize-js only tackles IIFE bu

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

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.

Install with Homebrew

brew install mongodb

Set up launchctl to auto start mongod

$ ln -sfv /usr/local/opt/mongodb/*.plist ~/Library/LaunchAgents

/usr/local/opt/mongodb/ is a symlink to /usr/local/Cellar/mongodb/x.y.z (e.g., 2.4.9)

	/**
	* This function loops over cart items, and moves any item with shipping class 'special-class' into a new package.
	* The new package in this example only takes flat rate shipping.
	*/
	function split_special_shipping_class_items( $packages ) {
	$found_item = false;
	$special_class = 'special-class'; // edit this with the slug of your shippig class
	$new_package = current( $packages );
	$new_package['contents'] = array();
	$new_package['contents_cost'] = 0;

	<?php

	/*
	* Note! This is no longer updated here in the Gist. It has been moved to a repo.
	*
	* @link https://github.com/daggerhart/wp-custom-menu-items
	*/

	/**
	* Class custom_menu_items

	Number.prototype.pad = function(size) {
	var s = String(this);
	while (s.length < (size \|\| 2)) {s = "0" + s;}
	return s;
	}

	(1).pad(3) // => "001"
	(10).pad(3) // => "010"
	(100).pad(3) // => "100"


	<!DOCTYPE html>
	<html ng-app="myApp">
	<head>
	<meta charset="utf-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
	<title>My AngularJS App</title>
	<meta name="description" content="">
	<meta name="viewport" content="width=device-width, initial-scale=1">
	<link href="//cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.2.0/css/bootstrap.min.css" rel="stylesheet" type="text/css"/>

	/*
	Purpose: add custom column header and custom column content to respective custom header in Manage Category Editing Page
	Version Tested: 3.8

	Story:
	Because I found no explanation nor documents in Wordpress.org, I tried to trace the code in wp-admin folder
	after understanding the operation of apply_filter(), add_action() and add_filter()

	Logic:
	The table list in edit_tag.php is based on

	# Change YOUR_TOKEN to your prerender token
	# Change example.com (server_name) to your website url
	# Change /path/to/your/root to the correct value

	server {
	listen 80;
	server_name example.com;

	root /path/to/your/root;
	index index.html;