As his extensive suite of benchmarks and product comparisons shows, this elegantly overcomes the problem of diminishing returns that come with adding more read-only slaves in a classic master-slave RDBMS replication setup without resorting to extensive use of non-relational solutions such as memcached.
Just kidding, he did it cuz it's fun to write cutesy JavaScript hacks that leak memory like hell and turn any machine slower than a Core 2 Duo into a paperweight.
I have a piece of paper stuck to the wall behind my desk that reads: "Research is blundering into an alley to see if it's a dead end". I think this falls into the same category. It's obviously not directly useful, but it might spark a thought in the creator or someone else that does lead somewhere.
And if not, well he probably had a good time coding it.
