Lotus Domino has got its knockers. Of which I've always been one. But, believe it or not, I'm also quite fond of it.
Back in January I said that I was no longer a Domino Developer. But then, in February, I was approached to do some Domino work. Nothing too taxing. A classic Domino website (customer still on version 8.0) that was pretty much a plain website. It didn't take long and I delivered it earlier this week.
Delivering the site was a doddle, as you'd expect, and was done on site - although it could easily have been done remotely. Such is the ease with which Domino apps can be deployed in to a live environment, it took me all of about 20 minutes.
Compare this with, say, an ASP.NET app's deployment, which would take quite a lot longer and involve FTP, RDC (for SQL database creation), IIS Manager. All very messy.
It's been nice being able to reminisce of how I used to work. I'm not saying I particularly miss Domino development, but there is a lot to be said for it. Domino is an amazing product: solid, reliable and simple to deploy, maintain and update applications.
It's a shame Domino is going the way it is really. And let's not pretend it's not. It's a dying product. I know we've all been saying this for 10+ years but now, really, come on, it's on the way out.
But hang on. Surely the fact I've just been asked to do a Domino job mean there's at least some work out there? Well, yeah, kind of. But even this customer is planning an imminent move to SharePoint. They just needed to get this one site online before then. Maybe it's the last Domino app they'll ever commission.
It's all a bit of a shame really.