remy

if (typeof window.localStorage == 'undefined' || typeof window.sessionStorage == 'undefined') (function () {

var Storage = function (type) {
  function createCookie(name, value, days) {
    var date, expires;

    if (days) {
      date = new Date();
      date.setTime(date.getTime()+(days*24*60*60*1000));
      expires = "; expires="+date.toGMTString();

saschagehlich

exports.I18n = 
  en:
    title: "Free YouTube video download"
    navi:
      home: "Home"
      howto: "Tutorial"
      blog: "Blog"
      termsofuse: "Terms of Use"
      support: "Support"
      imprint: "Imprint"

mathiasbynens

#!/bin/bash

if [ "$1" = "-h" -o "$1" = "--help" -o -z "$1" ]; then cat <<EOF
appify v3.0.1 for Mac OS X - http://mths.be/appify
Creates the simplest possible Mac app from a shell script.

Appify takes a shell script as its first argument:

    `basename "$0"` my-script.sh

ammmir

// generated user.js

function User() { // @extends Backbone.Model
  return Backbone.Model.apply(this, arguments);
}
User.prototype = Backbone.Model.prototype;
User.EMAIL_REGEX = /^(([^<>()[\]\\.,;:\s@\"]+(\.[^<>()[\]\\.,;:\s@\"]+)*)|(\".+\"))@((\[[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}\])|(([a-zA-Z\-0-9]+\.)+[a-zA-Z]{2,}))$/;
User.prototype.validate = function validate() {
  var email = this.get('email');

gvarela

# A sample Gemfile
source "http://rubygems.org"

 gem "redis"
 gem 'eventmachine', :git => 'git://github.com/eventmachine/eventmachine.git'
 gem "em-hiredis"
 # gem "em-synchrony"
 gem "em-websocket"

bergie

Some exercises from the Falsy Values workshops.

The good parts:

• HTTP server and client in same script
• Express cookies example
• Express routing example
• Express error handling
• Express middlewares example
• Simple HTTP proxy

gist:1073922

#include <math.h>
#include <stdio.h>
#include <string.h>

// buffer constraints
#define BUFFER_WIDTH 80 
#define BUFFER_HEIGHT 22 
#define BUFFER_SIZE (BUFFER_WIDTH*BUFFER_HEIGHT)

#define IMAGE_SCALE 15 

jcasimir

Sessions and Conversations

HTTP is a stateless protocol. Sessions allow us to chain multiple requests together into a conversation between client and server.

Sessions should be an option of last resort. If there's no where else that the data can possibly go to achieve the desired functionality, only then should it be stored in the session. Sessions can be vulnerable to security threats from third parties, malicious users, and can cause scaling problems.

That doesn't mean we can't use sessions, but we should only use them where necessary.

Adding, Accessing, and Removing Data

sofish

/**
 * @ NAME: Cross-browser TextStorage
 * @ DESC: text storage solution for your pages
 * @ COPY: sofish, http://sofish.de
 */
typeof window.localStorage == 'undefined' && ~function () {

    var localStorage = window.localStorage = {},
        prefix = 'data-userdata',
        doc = document,

necolas

NOTE I now use the conventions detailed in the SUIT framework

Template Components

Used to provide structural templates.

Pattern

t-template-name