bkeepers

#!/bin/sh
#
# Requires the `t` gem: https://github.com/sferik/t
#
#    gem install t
#

if [ -z $(t lists | grep -i githubbers) ] 
then
  t list create GitHubbers

churchofthought

I just finally had my mind snap into place with understanding of the Y Combinator. Most explanations I read, even the ones using JS, didn't make much sense and were overly long so here follows my own, much simpler explanation. I will be using JS.


We have fibonacci to start with, very simple recursive function.
It's fixed points are 0 and 1, fib(0) = 0, and fib(1) = 1
That's all a fix point means, when the f(x) == x
They are important because they are the only values at which recursion can cease.

Our Fibonacci Function
======================

gist:5202029

Going to use JS to explain.
We have fibonacci to start with, very simple recursive function.
It's fixed points are 0 and 1, fib(0) = 0, and fib(1) = 1
That's all a fix point means, when the f(x) == x
They are important because they are the only values at which recursion can cease.

Our Fibonacci Function
======================
function fib(x){
   return x + (x > 0 ? fib(x-1) : 0)

willglynn

# I split up jux.desktop-c2366d6aa995c5fe80506debabee8ee2.css into parts:
#  - one file for .theme-day
#  - one file for .theme-dusk
#  - one file for everything else
#
# My thought was that Jux.com could load the relevant theme CSS, and unload
# the unused theme(s). This would result in significantly fewer active CSS
# rules and some savings of data transfer without requiring much in terms of
# code changes.
#

lecram

#! /usr/bin/env python

"""{escher} -- one-file key-value storage.

What?
  This is a toy application to manage persistent key-value string data.
  The file {escher} is *both* the application and its data.
  When you run any of the commands below, the file will be executed and,
  after data change, it will rewrite itself with updated data.
  You can copy the file with whatever name to create multiple datasets.

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.

juliocesar

task :run do
  rackup  = Thread.start { `rackup -p 4567` }
  compass = Thread.start { `compass watch --sass-dir sass --css-dir css` }
  # ...
  at_exit { Thread.kill(rackup) and Thread.kill(compass) }
  sleep
end

# In the console, just run:
# $ rake run

davidjrice

# config/initializers/redcarpet.rb
module ActionView
  module Template::Handlers
    class Markdown
      class_attribute :default_format
      self.default_format = Mime::HTML

      def call(template)
        markdown = Redcarpet::Markdown.new(Redcarpet::Render::HTML, :autolink => true, :space_after_headers => true)
        markdown.render(template.source).html_safe.inspect

isaacs

# A bunch of the stuff above relies on this, especially the aliases.
[user]
  # you probably want to change this bit.
  name = isaacs
  email = [email protected]
  signingkey = 0x6C481CF6
[alias]
  ci = commit
  st = status
  br = branch

joerichsen

# -*- encoding: utf-8 -*-

Gem::Specification.new do |s|
  s.name        = 'parallel_assets_compiler'
  s.version     = '0.2.0'
  s.platform    = Gem::Platform::RUBY
  s.author      = 'Jørgen Orehøj Erichsen'
  s.email       = '[email protected]'
  s.summary     = 'Compile assets in parallel'
  s.description = 'Compile assets in parallel to speed up deployment'