jakearchibald

.whatever {
	-webkit-box-shadow: 0 2px 2px rgba(0,0,0,0.5) inset;
	-moz-box-shadow: 0 2px 2px rgba(0,0,0,0.5) inset;
	-o-box-shadow: 0 2px 2px rgba(0,0,0,0.5) inset;
	box-shadow: 0 2px 2px rgba(0,0,0,0.5) inset;
}

brettstimmerman

/**
 * Load a YUI Gallery module locally for testing.
 *
 * Assumes you've built your module with ant and have a local copy of the
 * yui3-gallery repo.
 *
 * This will override Loader's Gallery configuration. Existing Gallery modules
 * will load locally, and your new module should load locally as well.
 *
 * Props to Caridy for helping piece this together.

jakearchibald

<!--[if IE 8]><meta http-equiv="X-UA-Compatible" content="IE=7"/><![endif]-->
<!--[if gt IE 8]><meta http-equiv="X-UA-Compatible" content="IE=edge"/><![endif]-->

    I've been experimenting with this in a couple of projects.
    
    For animations, IE8 compat mode is noticeably quicker/smoother than
    IE8 strict. Since I still give 'full' support to IE7 (barring the
    odd text-shadow etc which IE8 doesn't support anyway) I use the tags
    above to push IE8 into compat mode for smoother animations, but allow
    the much faster IE9 to try its standardsy best.

darktable

application: you-app-name-here
version: 1
runtime: python
api_version: 1

default_expiration: "30d"

handlers:
- url: /(.*\.(appcache|manifest))
  mime_type: text/cache-manifest

kentbrew

Here be some notes on the insane set of gymnastics I have to go through every time 
I fuck up and start recording video with my iPhone held vertically.  

I do this a LOT.  I don't know why it happens.  Often I am standing over something and 
recording it, and the phone doesn't understand that I actually mean to hold it 
horizontally.

META QUESTIONS:

Why isn't there a way to prevent the phone from shooting video in vertical format?  Who 

ded

function r(f){/in/(document.readyState)?setTimeout(r,9,f):f()}

mrdoob

/**
 * Provides requestAnimationFrame in a cross browser way.
 * @author paulirish / http://paulirish.com/
 */

if ( !window.requestAnimationFrame ) {

	window.requestAnimationFrame = ( function() {

		return window.webkitRequestAnimationFrame ||

remy

function parseCSS(str) {
  function trim(str) {
    return (str||'').replace(/^\s\s*/, '').replace(/\s\s*$/, '');
  }

  var i, j, k, 
      split = '}',
      cur_key = '', 
      cur_key_split, 
      css = str.replace(/\t*/g, '').replace(/\s{2}/, ' ').replace(/[\n|\r]/g, ' ').replace(/\/\*.*?\*\//g, '').split(split),

chriseppstein

if ENV['RAILS_ENV'] && !defined?(RAILS_ENV)
  Object.const_set("RAILS_ENV", ENV['RAILS_ENV'])
end

# Require any additional compass plugins here.
require 'grid-coordinates'
require 'compass-fancybox-plugin'
require 'susy'

project_type = :rails

kentbrew

The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024. How, then, could I get Node talking on port 80 on EC2? (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)

The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

}).listen(80);