The Boston Diaries

The ongoing saga of a programmer who doesn't live in Boston, nor does he even like Boston, but yet named his weblog/journal “The Boston Diaries.”

Go figure.

Wednesday, Debtember 31, 2003

This version, that version, the-other version

I've thought a lot about “what went wrong” with svn (and take it as axiomatic, on this list, that something went wrong) for two reasons: (1) like Bob, I really tried to like svn; (2) as I started to think about “what went wrong”—it seemed like what went wrong was a bunch of mistakes of exactly the sort that I am inclined towards myself and therefore have to actively resist: there, but for the grace of something, stand I.

Here's what I think went wrong. This is just my unscientific impression based on following news of the project over the years.

Via Ceejbot, diagnosing svn

Those that are used to source control are pretty much in agreement that CVS sucks. I myself don't really have an opinion about CVS as it does all that I want it for and was painless to install and get running. Mark can't stand CVS and has been singing the praises of Subversion for some time now. I myself have been a bit leary of Subversion, if only because it's not something I feel I need to use; Mark, on the other hand, is used to working on huge projects (he's used to ClearCase) and feels he needs version control for what he does. For that, I have no problem.

But … Subversion isn't the easiest of packages to install. And Mark would be the first to agree with that. It took him several days of concerted effort to install a Subversion server, and even then, it pretty much requires a dedicated server of some hefty proportions to run. Even installing a client takes some work.

And the memory requirements (I've read that in some cases, over 300M of memory can be consumed) leave me wondering just what the heck Subversion does that requires such a hefty server configuration? I know I'm heading into a Dilbertesque Managerial mindset whereby what I do not understand must be trivial to implement, but still, the requirements for Subversion seem way excessive to me.

Now, I have hears some good things about arch; supposedly it handles everything Subversion does, isn't as bad as CVS and is easy to install. It seems pretty easy to me—one executable.

We'll see …


Tunnelling under FAU

From: XXXXX <XXXXXXXXXXXXXXXXXX>
To: sean@conman.org
Subject: Re: FAU Steam Tunnels?
Date: Wed, 31 Dec 2003 11:56:51 +0000

Woohoo! We did it! We almost got caught too, check out the full report on the site:

http://uef.hyposomnia.com

or if you prefer, here's a direct link to that update:

http://spork.no-ip.com/~uef/gallery/fau_utility_tunnels

… We saw pretty much the whole system with the exception of a few minor side branches that didn't really seem to go anywhere. There is in fact asbestos down there, so that kinda sucked, but most of it looked to be in good condition, so it's probably not a big deal if you take a trip or two down there without a respirator mask.

Obligatory Picture

[It's the most wonderful time of the year!]

Obligatory Contact Info

Obligatory Feeds

Obligatory Links

Obligatory Miscellaneous

You have my permission to link freely to any entry here. Go ahead, I won't bite. I promise.

The dates are the permanent links to that day's entries (or entry, if there is only one entry). The titles are the permanent links to that entry only. The format for the links are simple: Start with the base link for this site: http://boston.conman.org/, then add the date you are interested in, say 2000/08/01, so that would make the final URL:

http://boston.conman.org/2000/08/01

You can also specify the entire month by leaving off the day portion. You can even select an arbitrary portion of time.

You may also note subtle shading of the links and that's intentional: the “closer” the link is (relative to the page) the “brighter” it appears. It's an experiment in using color shading to denote the distance a link is from here. If you don't notice it, don't worry; it's not all that important.

It is assumed that every brand name, slogan, corporate name, symbol, design element, et cetera mentioned in these pages is a protected and/or trademarked entity, the sole property of its owner(s), and acknowledgement of this status is implied.

Copyright © 1999-2022 by Sean Conner. All Rights Reserved.