JosephPecoraro

# Ways to execute a shell script in Ruby
# Example Script - Joseph Pecoraro

cmd = "echo 'hi'" # Sample string that can be used

# 1. Kernel#` - commonly called backticks - `cmd` 
# This is like many other languages, including bash, PHP, and Perl
#   Synchronous (blocking)
#   Returns the output of the shell command
#   Docs: http://ruby-doc.org/core/classes/Kernel.html#M001111

mojombo

require 'digest/md5'

def gfm(text)
  # Extract pre blocks
  extractions = {}
  text.gsub!(%r{<pre>.*?</pre>}m) do |match|
    md5 = Digest::MD5.hexdigest(match)
    extractions[md5] = match
    "{gfm-extraction-#{md5}}"
  end

steida

/*
*   Sugar for type detection working across frames and browsers ;)
*
*   Detected types
*
*       'arguments', 'array', 'boolean', 'date', 'document', 'element', 'error', 'fragment', 
*       'function', 'nodelist', 'null', 'number', 'object', 'regexp', 'string', 'textnode', 
*       'undefined', 'window'
*
*   Copyright (c) 2009 Daniel Steigerwald (http://daniel.steigerwald.cz), Mit Style License

nkallen

/* This is when a refactoring really pays off.
 *
 * In order to make your code more modular, avoid hard-coding assumptions (or refactor them away).
 * The most fundamental, anti-modular assumption in Object-Oriented software is the concrete type of objects.
 * Any time you write "new MyClass" in your code (or in Ruby MyClass.new) you've hardcoded
 * an assumption about the concrete class of the object you're allocating. These makes it impossible, for example,
 * for someone to later add logging around method invocations of that object, or timeouts, or whatever.
 * 
 * In a very dynamic language like Ruby, open classes and method aliasing mitigate this problem, but
 * they don't solve it. If you manipulate a class to add logging, all instances of that class will have

nicksieger

# Monkeypatch to disable connection pooling in ActiveRecord
module ActiveRecord
  module ConnectionAdapters
    class ConnectionPool
      def checkout
        c = ActiveRecord::Base.send(spec.adapter_method, spec.config.dup)
        c.verify!
        c
      end

headius

require 'rubygems'
require 'spoon'

Spoon.spawnp 'jruby', *ARGV

padolsey

// ----------------------------------------------------------
// A short snippet for detecting versions of IE in JavaScript
// without resorting to user-agent sniffing
// ----------------------------------------------------------
// If you're not in IE (or IE version is less than 5) then:
//     ie === undefined
// If you're in IE (>=5) then you can determine which version:
//     ie === 7; // IE7
// Thus, to detect IE:
//     if (ie) {}

nicksieger

JRuby Memcached Client Benchmark Notes

These benchmarks were run using a modified copy of Ruby Memcached's test/profile/benchmark.rb that adds several JRuby-only clients into the mix.

The benchmarking script also runs an Ehcache client for (an unfair) comparison. Ehcache is a configurable Java-based cache, and runs in-memory for this benchmark using the jruby-ehcache-rails3 gem.

The benchmarks were run with the JVM's server (optimizing) compiler. Since the JVM warms up as it goes, later runs are smaller and take into account the warmup.

For cross-Ruby comparison I also ran the same script to exercise the Ruby Memcached/libmemcached client using Ruby 1.9.2-p0.

thinkerbot

# Two ENV variables control the 'gem' command:
#
#   GEM_HOME: the single path to a gem dir where gems are installed
#   GEM_PATH: a standard PATH to gem dirs where gems are found
#
# A gem directory is a directory that holds gems.  The 'gem' command will lay
# out and utilize the following structure:
#  
#   bin               # installed bin scripts
#   cache             # .gem files  ex: cache/gem_name.gem

briandealwis

# turn a jar with a Main-Class into a stand alone executable

(echo '#!/usr/bin/env java -jar'; cat blahblah.jar) > blah

# turn a jar with a particular main clas into a stand alone executable

(echo '#!/usr/bin/env java -jar package.MainClass'; cat blahblah.jar) > blah