- resource bundles for devices
- rely on UA and server-side processing

- opera mobile transfer binary data to client
- webp support in opera and chrome
- webp features: sprites, animations, stereoscopy

- scribe logging directly to HDFS
- puppet for configuration
- reviewboard for code reviews
- majority open source
- mysql w/ lots of memcached (now redis)

- interfaces do not have to be explicitly declared: simplifies testing
- you can attach methods to any type in your package / extend via your own type interface
- timeout primitive to force a deadline on a channel
- Go does not expose asynchronous API's, instead sync api's are wrapped in Goroutines
- great example of distributed search: serial > replica searches > deadlines

- "a game is a series of interesting decisions"
- give users ability to personalize
- there are many player types: listen to each, but focus on own design
- decisions as tradeoffs: short-term for experimentation, provide lots of information for long-term

- everyone is thinking in objects
- what if our OOP languages limited the number of active objects? like we do with concurrency
- what would happen if we remove the concurrency limitation - aka lightweight processes
- Kuhn's paradigm shifts: applies to how we think and deal with concurrency

- webgl based on OpenGL ES 2.0 spec
- vertex shader + fragment shader (pixel)
- upload vert and fragment shader source to the GPU, bind the data, draw the triangle
- particle systems: incorporate time into the shader and translate the vertex within the shader
- fragColor = fragment color
- many triangles are larger than a pixel, hence rendering at pixel level can yield better visual results
- IE does not support WebGL, have to use chrome frame

- mix of native and web for different platforms
- scrolling done in native on iOS for performance
- "screen JSON" as a single response to render all required components on the page (node.js aggregator service)
- apps built on same public APIs as rest of platform
- performance still lagging behind native
- android 80% native due to lack of hardware accelerated CSS3 on 3.x devices
- phantom.js for performance testing

- opengl developed as a cross-industry standard (chronos group)
- 3 points to unambiguously define the plane - hence the triangle mesh
- programmable shader instead of built-in heuristics: switch from opengl 1.1 to 2.0
- programmable shader allows you to upload code for how to render a triangle point
- two pieces of code: one to determine lighting, one to rasterize to pixel
- webgl uses canvas tag, can be overlayed on top of regular html content
- webcl for physics and/or customized kernels (ex: deformed body simulation)
- focus on security: can't access outside memory, etc

- users perceive load time to being about 15% slower than actual time
- recounting the experience will show 35% slower

Three second rule - 57 percent of online shoppers will wait three seconds or less before abandoning the site