Upgrading Software
Dear Reader,
Well, it’s the weekend so I naturally decided to check what software needed upgrading. Two packages quickly showed up on my “things I use and keep current” list.
Spaz
Ed Finkler wrote this cool little twitter client and compiled it using AIR. Despite the fact that AIR has some kind of seriously dmanaged garbage collection requiring me to restart Spaz every hour or so, I love this little app. Ed has done some cool thing with it and I enjoy watching it’s progress. The only think I don’t like is when there is a new version (say…24 hrs has passed) when I fire it up, I get an in-your-face notification requiring me to decide at that moment, “Upgrade or No?” It’s not that I have anything against upgrading and certinly not against Ed or Spaz. but an icon on the toolbar when there is an upgrade available would be much nicer. Besides, I fired the client up to use it…not decide whether I wanted to upgrade. And yes, I know it’s Open Source software so I’m not griping about it or demanding a refund, I’m just using it as an example because the Windows Upgrade example has been beat to death.(BTW: Yes Ed, I’m jealous. I wish I had a cool open source app that everybody could point out the flaws of but never give me props for.)
Wordpress
I like Wordpress. Despite it’s flaws and the fact that I think Matt is a bit unstable because he won’t upgrade it to work exclusively on PHP 5, I really like it. However, for the uninitiated, installing or upgrading it manually can be difficult. I have a good friend who shoots up “The Bat Signal” whenever he runs into a programming problem and I got one this morning. He tried to move from 2.3 to 2.3.1 and it was (shall we say) less than graceful. On the other hand, I upgraded both of my blogs in about 2 minutes. It actually too me longer to upgrade one of my plugins than it did my two blogs. This is, of course, thanks to the fact that I use Installatron on my server. Installatron makes keeping these types of applications up to date, extremely easy.
A side note on Wordpress, while it has an annoying “you need to upgrade” link on every admin page when there’s a new version, it does not force me to decide whether to upgrade before I can do anything else.
Anyhow, both this blog and PHP Podcasts have been upgraded and I even had time to add a shinny new skin here. (Didn’t really like the last one) So life is good…mostly.
Until next time
(l)(k)(bunny)
=C=
![[Post to Twitter]](http://blog.calevans.com/wp-content/plugins/tweet-this/icons/tt-twitter-big4.png){kind=icon}
Related posts
Tags: ed finkler, PHP, spaz, upgrade, wordpress
November 3rd, 2007 at 3:25 pm
Of all the things I’ve learned and subsequently forgotten in the world of upgrading, the most valuable is the lesson learned by your example: When possible, let the installers take care of it. Same goes for hardwood floors. There’s a reason for automation of painful tasks, and it’s just crazy not to take advantage of automated software installers if they work, as they always have in my experience. And by the way, don’t think I’m unaware of your routine three-hour-wait-to-see-if-he-figures-it-out-on-his-own delay to my many bat signals. I might have to start applying the delay myself. Like I say — I’ve learned so much from Cal!