state of the art — isn’t

I’d never paid attention to certain version numbers, and release dates, of certain applications. And, frankly, always assumed that things were up to date.

Apparently, that assumption was likely mistaken.

$ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)
Copyright (C) 2007 Free Software Foundation, Inc.


The copyright on that specific version on the state of the art macos — all Macs — was 2007. TWELVE years ago.

What version is currently available? Unsure, but I’m going to bet that it’s most certainly not v3.2.57(2).

Ah, yes… it’s slightly newer:

Isn’t quite as state of the art having GPL-software that’s static. Yeah, I know, it makes things more stable. I get it. But there will be some newer capabilities, improvements, bug patching and so forth that will be revealed with the continuing march of progress.

Now… what are the risks to doing the upgrade?

[Edit: Well, I’m certainly not the first to see this and I only started pondering it when I wanted to make kubectl auto-complete available directly. Probably a good idea to upgrade.]

Still Funny

We’re using Hubot for very limited automation and integration with our messaging apps. We’ve renamed it from “hubot” to “alfred”.

To make a request, you simply begin with “alfred …” Like, for example, you need it to build a cluster, the instruction might be alfred build <region> <name> Of course, the ‘region’ and ‘name’ are variables that you’ll define when running it. You could even just do alfred help to get a complete list of every defined process that it’s capable of. Really simplistic, honestly.

But the confusion that arises just from the bot’s name is amusing. People mistakenly (accidentally on purpose?) type things like:

  • albert build us-west-2 devcluster
  • alvin build eu-west-1 mycluster
  • althea help
  • alexa do the build

Heh… remember that SNL skit from a couple of years ago? Same thing, really: