Brian M Hunt brianmhunt

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.

Element APIs

Getting box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent

APPENGINE_RUNTIME	python27
APPLICATION_ID	s~appid
AUTH_DOMAIN	gmail.com
CONTENT_LENGTH	148
CONTENT_TYPE	application/x-www-form-urlencoded
CURRENT_MODULE_ID	default
CURRENT_VERSION_ID	appid.370290628632119235
DATACENTER	us1
DEFAULT_VERSION_HOSTNAME	appid.appspot.com
HTTPS	on

Lesson's learnt building the Guardian

Below is a collection of my favourite responses I gathered from Guardian engineers when asked the question: What have you learnt starting from scratch and building a mobile-first next generation web platform for the Guardian?

Daithi O Crualaoich

Work with great people.
Deploy like crazy. This means the team has to control the infrastructure as well as code.
Design is not a service. Designers have to sit in the team.
Infrastructure is intrinsically unreliable. Discard and replace is the robust strategy.
Use your CDN for HTML too.
Don't always do as you are told.

Business Models

Advertising

Models	Examples
Display ads	Yahoo!
Search ads	Google

This is a fork of Bootstrap Typeahead that adds minimal but powerful extensions.

For example, process typeahead list asynchronously and return objects

  # This example does an AJAX lookup and is in CoffeeScript
  $('.typeahead').typeahead(
    # source can be a function
    source: (typeahead, query) ->
 # this function receives the typeahead object and the query string

	{
	"jest": {
	"moduleFileExtensions": [
	"js",
	"json",
	"jsx",
	"node",
	"coffee"
	],
	"preprocessorIgnorePatterns": [ ],

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	package main

	import (
	"encoding/json"
	"fmt"
	"net/http"
	)

	type test_struct struct {
	Test string

	package main

	import (
	"encoding/base64"
	"net/http"
	"strings"
	)

	type handler func(w http.ResponseWriter, r *http.Request)