lsmith

// Step 1. global definition
function Map(config) {
    this._init(config);
}

Map.prototype = {
    _container: null,

    _init: function (config) {
        this._container = document.getElementById(config.container);

mythz

JS Conf slides - 2011

Track A

• Bytes and Blobs by David Flanagan
• Conference Wifi Redux by Malte Ubi
• Sashimi - https://github.com/cramforce/Sashimi
• Run Your JS everywhere with Jellyfish by Adam Christian - http://jelly.io Project
• Fighting Crime and Kicking Apps with Batman.js by Nick Small
• Hello Jo by Dave Balmer - Project - http://joapp.com

3rd-Eden

/**
 * Bootstrap app.
 */

require.paths.unshift(__dirname + '/../../lib/');

/**
 * Module dependencies.
 */

JerrySievert

coverage.json

Meta Data

Meta-data identifies the specifics of the coverage information, as well as the file versioning information.

{
  meta: {
    generator:       'vowsjs',

generated: 'Fri Aug 05 2011 22:45:56 GMT-0700 (PDT)',

natecavanaugh

{
	replaceStr: function(match, fragment, string) {
		return fragment + 'm=' + (match.split('<%= javaScriptRootPath %>')[1] || '');
	},
	searchExp: '(\\?|&)/([^&]+)'
};

chitchcock

Stevey's Google Platforms Rant

I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.

I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real

nzakas

<target name="compress">

    <!-- store filenames in a property delimited by ; -->
    <pathconvert pathsep=";" property="compress.jsfiles">
        <fileset dir="${build.dir}" includes="*.js"/>
    </pathconvert>    

    <script language="javascript"><![CDATA[

        importPackage(java.io);

isaacs

Stability ratings: 0-5

0 - Deprecated.  This feature is known to be problematic, and changes are
planned.  Do not rely on it.  Use of the feature may cause warnings.  Backwards
compatibility should not be expected.

1 - Experimental.  This feature was introduced recently, and may change
or be removed in future versions.  Please try it out and provide feedback.
If it addresses a use-case that is important to you, tell the node core team.

buritica

#!/bin/bash

# Open iPhone Simulator on default location for XCode 4.3 if found

[[ -d /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app/ ]] &&
	open /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app

# Open iPhone Simulator on default location for XCode 4.2 if found
[[ -d /Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app/ ]] &&
	open /Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone\ Simulator.app

marktheunissen

This playbook has been removed as it is now very outdated.