Recently, a coworker whipped up a Perl script that’ll build all of the
Perl modules we support. This is useful for when we add a new
supported OS or OS version. This script takes a config file, moduledefs, which lists the modules to build, as well as various quirks that affect how and whether the modules should be built. moduledefs is itself a `require‘d Perl script:
I propose the following new term: filibuster screen. It refers to an application splash screen, such as KDE’s or OpenOffice’s, which not only takes up a big chunk of otherwise-useful screen real estate for a long time while it starts up, but also ignores window manager hints so you can’t even move the bloody thing out of the way, thus preventing you from getting any useful work done.
I realize “filibuster screen” is a bit lame. If you can think of a better term, please say so in the comments.
If you wanted to evolve a musical composition — or better yet, if you wanted to evolve a piece of software that could write music on demand — how would you do it?
I came up with the following approach after reading Sean Carroll’s Endless Forms Most Beautiful.
I don’t always agree with Paul Graham, but his writings are often thought-provoking. One of the things he’s done recently is to rekindle my interest in Lisp and Scheme.
Read More