Jonathan Creamer jcreamer898

This is a small collection of scripts showing how to use require.js. It's only one of several ways of setting up a require.js project, but it's enough to get started.

At its core, require.js is about three things:

Dependency management
Modularity
Dynamic script loading

The following files show how these are achieved.

Updated for Rails 4.0.0+

Bower

Set up the bower gem.
Follow the Bower instructions and list your dependencies in your bower.json, e.g.
```
// bower.json
```

{

Speaker Bio - Jordan Kasper

Jordan started programming in 1993 and has developed systems on platforms ranging from IBM mainframes to TI calculators and everything in between. Jordan's experience includes software development, instruction, mentorship, and technical leadership at startups, Fortune 100 companies, universities, and state and federal governments. He is an open source maintainer and regular conference speaker. Outside of work Jordan is a community organizer, board game enthusiast, and aspiring author.

Gov Version

Jordan Kasper started programming in 1993 and has developed systems on platforms ranging from IBM mainframes to TI calculators and everything in between. His professional experience ranges from startups and digital agencies, to Fortune 100 companies and both state and federal government agencies. Most recently he worked for the Departments of Defense and Homeland Security where Jordan helped to reform struggling IT programs, advocate for modern technology and practices, advise on

Animated Gifs

This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.

You're Missing the Point of Promises

Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:

getTweetsFor("domenic", function (err, results) {
 // the rest of your code goes here.


	<?xml version="1.0" encoding="UTF-8"?>
	<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
	<plist version="1.0">
	<dict>
	<key>comment</key>
	<string>
	TODO: unresolved issues

	text:

	-module(bowling).
	-export([main/1]).

	main(_) ->
	test().

	test() ->
	% empty
	[] = score([]),
	% boring

	// OOP
	console.log( 'OHAI'.blink() );

	// Call invocation
	console.log( String.prototype.blink.call('OHAI') );

	// $ always makes things look awesome.
	var $ = Function.prototype.call;

	// Very explicit call invocation

	// Require.js allows us to configure shortcut alias
	require.config({
	// The shim config allows us to configure dependencies for
	// scripts that do not call define() to register a module
	shim: {
	'socketio': {
	exports: 'io'
	},
	'underscore': {
	exports: '_'

Jonathan Creamer jcreamer898

Bower

Speaker Bio - Jordan Kasper

Animated Gifs

You're Missing the Point of Promises

Whitbeck’s Law

If it exists, there is a GIF of it.

Manor’s Law

For every message there is an equal and opposite deletion.

Cowart’s Law

All great messages will be deleted before you have a chance to read them.

Neiner’s Law