Building notes, projects, and ocasional rants


last update:


Jack Moffitt was bitten by auto-save. My auto-save setup is "Save when TextMate looses focus" but yesterday I was scripting something better that will be a great auto-save post-script. When I start to work on something experimental, I would like to have a snapshot of every path I take and undo. Sometimes I write some code, and then say "naahhh, wont work ok", and undo it, without any record. And this is bad, because some of those actually were a good path after all.

Memory tricks

Interesting read to catch up on current PC architecture. Favorite quote: One developer we consulted about the issue noted, "consumers are being scammed by [PC] OEMs on a large scale. OEMs will encourage customers to upgrade a 2GB machine to 4GB, even though the usable RAM might be limited to 2.3GB. This is especially a problem on high-end gaming machines that have huge graphics cards as well as lots of RAM.

I'm re-factoring an old site where the art of source control went out the window somewhere in the past. The current problem I'm trying to solve is multiple versions of the lib/ directory, each one with their own copies of the same .pm files, but some of them with local modifications. As a first step I want to create a single central lib/ that will take files that are the same on all the other directories.

Google and WebKit: a love story?

With a 38 page comic, you can get to know a bit about Google Chrome, the Google browser. Highlights: uses WebKit as renderer;it has his own JS engine, written by Team V8, and it includes a JIT;each tab is a separate "process" running inside a jail or sandbox;Gears is built-in;allows to run Web-based app in a chrome-less window;project completely open-source: I think they mean source available, but maybe I'm a pessimist regarding Google openness.

Pretty and useful

If you thrive to achieve a stress free life, and keep programming at the same time, I assume that you know how automated testing and test-driven development are an essential tool. I've been using them for most (not all) of what I do in the last year or so. Basic stuff, using Test::More and friends, and more recently Test::Most and using the basic prove tool and Devel::Cover for extra peace of mind.


The guy who won $275.000 on the Google Android contest (english translation): Asked what he would do with the cash, his response was “I guess I could invest it in my software company, but first I want to port PicSay to the iPhone.” Priceless... (via daring fireball) Update: the PicSay author clarifies the whole story.

Pretty print XML

In case you didn't know, you can pretty print XML with the xmllint command line tool that comes with libxml2, and its installed by default with Mac OS X. Basic usage is xmllint --format xml_file.xml and the pretty version will be sent to standard output. But working with XMPP and SAPO Broker, I'm always copy&pasting XML from one place to the other and it would be nice to format the XML snippet sitting in the clipboard.


Mozilla Labs Ubiquity looks very nice indeed. I wonder how hard it would be to port it to a Fluid plugin? (via Ajaxian)


The bounty for the first verifiable security problem found in djbdns increased from $500 to $1000. I offer $1000 to the first person to publicly report a verifiable security hole in the latest version of djbdns. For us Europeans, it stays the same actually.