To my surprise, most Linux-related podcasts are really, really bad.
This surprises you how exactly? Linux users are almost never involved in media production, most coming from orthodox IT-related areas. I do a lot of creative production work, and I have to laugh every time I talk to somebody who is both a Linux user (as I am), really into tech, and somehow passionate about getting something produced. They really have no clue what is up or down, and most of their anecdotes come from being really pissed off by Flash-driven websites, even when they ARE dealing with time-bound, linear media where something like an "animated intro" is considered a staple of production. I still chuckle about it.
This is the first time I've actually heard of people complain about actual lose-your-work crashes.
Actually I think most of the lost work in our case comes from factors external to Photoshop. In our labs, we usually see hardware problems crop up and cause loss of work long before a Photoshop stability problem occurs.
However, if Adobe kept a big Trac or Bugzilla site somewhere, and even if it just showed bugs from labs where I teach, I think the reliability point would get across. There are just some awful bugs in the software, and as you mentioned, Photoshop is complex enough that workarounds aren't hard to find once the issue has been isolated. But man, you should see some of my students when they lose work. I think this is why Adobe provide versioning software now. Support can say, "so do your backups not work then?" [long pause, phone line goes dead]
Dynamically binding, you realize the magic. Statically binding, you see only the hierarchy.