Read on and leave a comment
or return to our portfolio.

Archive for June, 2006

14 Jun 2006

by Noel

When It Rains It Pours

Yesterday we though we were about to go live on our biggest application yet. The code has been installed on the client’s server, it has been tested, and we think it’s all ready to go. Then is starts raining down in London. You wouldn’t think rain in Britain would be any big deal, but not so. Somehow the rain finds its way through a couple of storeys of building into the client’s server room, and yes, drenches our server. Then the power goes out. Net result is a server that won’t boot up when it finally dries out. Luckily Dave happens to be going down that way, and so finds himself in London installing the software on a spare machine the client had. We think we’ll still make the Thursday lauch date, but only just.

Posted in Business | Comments Off on When It Rains It Pours

6 Jun 2006

by Noel

OO is convenient

One of the recurring themes of the Dagstuhl workshop was “convenience matters”. This is clearly true. All Turing complete programming languages have equivalent power yet we prefer some over others. It’s about what they make easy.

This point came to mind when looking at the various abstraction mechanisms in PLT Scheme. The designers of PLT Scheme have analysed the types of abstractions people often use, carefully separated them into different classes, and provided separate mechanisms for each class. If you want to create a unit of functionality you can use the module system. If you want to parameterise code you can use the unit system. If you want to dispatch on type you can use the OO system. This is in contrast to Java, where you get one main abstraction mechanism, the class, which is a module system, a way of parameterising code, and a dispatch mechanism all mashed up into one. This is considered undesireable as you are forced to consider interactions with other mechanisms when you only want to use one. However it has one big advantage: convenience. I don’t often use PLT Scheme’s unit system, so when I do I have to look up the documentation. Same with PLT’s OO system. This tends to make me avoid using them, as I don’t like to spend time reading the docs or figuring out the system. However with Java you’re always writing classes, so it’s familiar and the barrier to use is lower. Convenience matters.

Posted in Web development | Comments Off on OO is convenient