Francis Hwang once posted an item about modifying Ruby's require method so that you can load files over HTTP (or, really, pretty much any file transfer protocol).

It's really quite clever. I think, though, that having to explicitly include the protocol scheme and path when calling require spoils half the fun.

My take on this is to alter Kernel#require so that it knows to look for requested files outside of the local file system.

# File: hyperactive-require.rb
require 'open-uri'

def require( resource )
  rescue LoadError
    $:.each do |lp|
      if lp =~ /http:///i
          lp << '/' unless lp =~ //$/
          s = open( "#{lp}#{resource}" ) { |f|}
          eval s
        rescue; end
    raise "Cannot find '#{resource}'")

The trick here is that the load path must be given one or more Web addresses; these sites will then become just more places to look for code. Aside from that, client code does not need to know if some required file is local or remote.

A nice side-effect: No more installations. Well, maybe fewer, simpler installations. Distribute a basic script, define the appripriate URLs, and have it require the app libs as if they were local. You could also switch library version by changing LOAD_PATH URLs to fetch from different repositories.

Dangerous? Um, perhaps. But c'mon, it's a new year. Live it up!

Besides, everyone knows how dangerous Ruby is . So dangerous that, in the spirit of the season, I even dreamed up Yet Another Ruby Motto.

Ruby: You'll Shoot Your Eye Out.

So let's try an example and see if we lose an eye or something.

# File: trusted-sites.rb
# I trust these guys!
}.each { |uri|
 $:.push uri

# File: example.rb
# See if we can grab my RSS feed

require 'hyperactive-require'
require 'trusted-sites'
require 'vsocial' 

vs = 'jamesbritt' )
puts vs.rss

Whew! Scary, but no ocular mishaps. It's certainly no worse than running with scissors.

One side detail: The hyperactive-require code issues an HTTP request for a file with no extension, but it is likely that the actual source file on disk at the server will end in .rb. I used the MultiViews option with Apache2 to allow the server to return a disk file with a .rb extension even if the request URL did not specify that.

Oh, and note, too, that file requests going through an intermediary process opens the door for all sorts of entertainment. You could, for example, dynamically assemble the code returned, perhaps returning different versions based on the client's IP address. Or have the server invoke a CVS or Subversion checkout to grab the latest code. Or send back a new version of Kernel#require or another set of LOAD_PATH URLs.

Or something. Just don't hurt anyone.