Time to blow off some dust of this blog once again. Hopefully, more interesting content coming very soon.

Here's a micro-rant. I've probably written about this before, but it's worth repeating.

I've taken a few looks at some of the interesting open source software packages lately. For example, I've idly been wondering if there are actually feasible alternatives to Drupal - not that I'd be in any hurry to move away from it. Also, upgrading webware is a pain in the ass, so I wondered if I could apply some enterprise solutions to it, like Puppet.

So after some thorough digging on the Puppet wiki, one thing becomes pretty damn apparent: nope, the damn thing doesn't do what I'd want it to do. I want to apply software updates on servers I have an ssh/command line access to and can't run daemons on. I'm in an environment that is enterprisey but not that enterprisey.

So why the fuck isn't this part of Puppet's marketing material? This is crucial information that I need. The home page basically pushes a gigantic VM image on my face. "Download this 10 gigabyte disk image and then make the amazing discovery that this fucking thing cannot be deployed on your puny setup."

If the marketing web page says "remote systems running a daemon", I know to skip the damn thing. If the marketing page says "only needs sshd and rsync (or whatever) in the remote end", sold. But if I need to specifically go and dig for information for half a hour and/or download a gigantic demo, and then find out that the system needs pretty extensive setup in the remote end, I know to a) skip the damn thing and b) curse the bastards for making me waste my time.

The exact same thing was apparent when I was looking for the CMS stuff. Oh, sure, I found several nice CMS packages, make no mistake. It's just that most of them seem to market themselves pretty extensively on their home page as the last damn CMS you need and how nice everything really is. ...and only twenty pages later you find out that it's PHP and MySQL. I'm trying to move away from CMSes written in PHP. This is crucial information. Why is it withheld?

So dearest remoteware makers: tell me what the hell I need to deploy the damn things. System requirements go to the first page of the installation guide, and if this information is crucial enough to be the first entry in the installation guide, then sure as hell it should be the first thing prospective users want to know. They want to know if they can run the damn thing in the first place. Not rocket science.

Okay, end of pointless rant. More pointful blogging to follow soon, I hope.