nodeconf slides - 2011
a list of slides from nodeconf
you may want to take a look at the jsconf-gist too!
|diff -U 0 -r rails-3.1.0.rc4/Gemfile rails-3.1.1/Gemfile|
|--- rails-3.1.0.rc4/Gemfile 2011-10-07 12:02:26.000000000 -0400|
|+++ rails-3.1.1/Gemfile 2011-10-07 12:59:13.000000000 -0400|
|@@ -3 +3 @@|
|-gem 'rails', '3.1.0.rc4'|
|+gem 'rails', '3.1.1'|
|@@ -10,4 +10,8 @@|
|-# Asset template engines|
|-gem 'sass-rails', "~> 3.1.0.rc"|
This installs a patched ruby 1.9.3-p327 with various performance improvements and a backported COW-friendly GC, all courtesy of funny-falcon.
You will also need a C Compiler. If you're on Linux, you probably already have one or know how to install one. On OS X, you should install XCode, and
brew install autoconf using homebrew.
A slightly updated version of this doc is here on my website.
I visited with PagerDuty yesterday for a little Friday beer and pizza. While there I got started talking about Go. I was asked by Alex, their CEO, why I liked it. Several other people have asked me the same question recently, so I figured it was worth posting.
The first 1/2 of Go's concurrency story. Lightweight, concurrent function execution. You can spawn tons of these if needed and the Go runtime multiplexes them onto the configured number of CPUs/Threads as needed. They start with a super small stack that can grow (and shrink) via dynamic allocation (and freeing). They are as simple as
go f(x), where
f() is a function.
|desc 'rolls back migrations in current branch not present in other'|
|task :rollback_branch_migrations, [:other_branch] do |t, args||
|branch_migrations = BranchMigrations.new(args.other_branch)|
|puts ['Rollback the following migrations', branch_migrations, 'y,n? ']|
|next if %w[no n NO N].include?(STDIN.gets.chomp)|