TooTallNate

#!/bin/sh

VERSION=0.8.6
PLATFORM=darwin
ARCH=x64
PREFIX="$HOME/node-v$VERSION-$PLATFORM-$ARCH"

mkdir -p "$PREFIX" && \
curl http://nodejs.org/dist/v$VERSION/node-v$VERSION-$PLATFORM-$ARCH.tar.gz \
  | tar xzvf - --strip-components=1 -C "$PREFIX"

voidfiles

How you can create a responsive grid system using YUI3 grids and SASS

This is a quick rundown of how and why we use YUI3 grids at App.net

As far as I can tell there are three types of CSS grids: a static-width pre-defined grid, a flexible-width pre-defined grid, and a generative grid. In the first two grids (pre-defined width), you basically decide how many columns you have across the screen, and then create blocks in any multiple of those. This pattern often looks like "span-4", "span-6", "pull-10", "push-5", etc. You find this style in popular frameworks like Bootstrap and Blueprint.

The third way, the generative/recursive grid system, doesn't seem to be as popular as the others. I am not entirely sure why, because the generative grid can pack more punch in less lines. In this vein is there is OOCSS and YUI3 CSS Grids.

botic

include("ringo/subprocess");

var log = require("ringo/logging").getLogger(module.id);

exports.app = function(req) {

    log.info("Incoming request.");

    if (req.method !== "POST") {
        log.info("Not a valid POST request.");

antoniosilveira

>>> import stripe
stripe.api_key = "vtUQeOtUnYr7PGCLQ96Ul4zqpDUO4sOE"
stripe.Charge.create(
  amount=400,
  currency="usd",
  card={
    "number": '4242424242424242',
    "exp_month": '12',
    "exp_year": '2012',
    "cvc": '123'

adamlogic

Compass and CSS Sprites, Explained

Last week I attempted to use the CSS sprites feature of Compass for the second or third time. It's been a struggle each time, but the power and potential is there, so I keep coming back. This time was a bit different, though, because I finally decided to stop relying on the docs and dive into the code.

Before I go into the nitty-gritty, let's take a step back and talk about why I

devongovett

/*
 * RSS Subscription Count Node.js Proxy Server
 * Devon Govett
 * Public Domain
 *
 * This script is a simple proxy server for my blog's RSS feed that keeps track of requests
 * to the feed and attempts to guess a subscriber count.
 * Google Reader represents the majority of my subscriber base, and they give you actual
 * subscriber numbers when their spider requests your feed.  Other aggregators do something similar.
 * Otherwise, this script tracks unique IP addresses over a 24 hour period.

jlong

//
// Sass rotation mixin for IE6+
//

@mixin ms-rotate($degrees) {
  @if (not unitless($degrees)) { $degrees: $degrees / 1deg }
  $deg2rad: pi() * 2 / 360;
  $radians: $degrees * $deg2rad;
  $costheta: cos($radians);
  $sintheta: sin($radians);

domenic

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.

cbetta

git mv readme.md readme.md.temp
git mv readme.md.temp README.md

evilmarty

If like me you find it frustrating to define the same vendor prefixes over and over again. Sure, you might create mixins that help reduce the amount of repetitiveness but when your mixins file becomes a library (or not) you see so many lines of near-identical code and wonder if there is an easier way.

Say you have this (all-too familiar) mixin:

@mixin border-radius($radius) {
  -webkit-border-radius: $radius;
  -moz-border-radius: $radius;
  -ms-border-radius: $radius;
 -o-border-radius: $radius;