FM RadioStation was useful enough for me to recommend it, but I just stopped using it after a week.  Why?  Because it was too slow to start.  I usually run Radio only when I am about to post something and Radio is slow to start itself.  With RadioStation, I have to wait twice as long before I can write my post.  I am also not too happy with amount of memory and CPU cycles both programs use.

Programmers certainly have gotten sloppy with resources over the years.  I don't expect them roll assembly code nor am I expecting extreme frugality like Steve Gibson, but people need to remember that speed and small footprint are important features.  Speed, particularly, is making a come back now if popularity Apple's Safari is any indication.

Acrobat is another program that could use some speed.  Imagine much happier Acrobat users will be if it was twice as fast.  Microsoft Office suite is also a pack of dogs when it comes to speed.  Just try saving a word file as a text file using a non-English encoding.  A dialog pops up with a list of encodings, a few checkboxes, and a preview.  Depending on the size of the file, I have to wait 10+ seconds before I can click on anything, and another 10 seconds after selecting an encoding.  Are they out of their minds?  If an Office-killer appears in the future, speed will be a big part of it.

Prototyping is good and incremental development is good, but one must occasionally refactor or rewrite to keep the software alive.  Dave should consider rewriting Radio from scratch using Python.