I guess there's a growing flap about VB6 being decomissioned and becoming unsupported. The Mountain of Worthless Information has a good summary (and is where I learned of it).
It all goes back to what I've said time and time again; if you're building important, core business applications, choose a platform that's going to be around a while. If Microsoft is going decommision VB6 after 7 years, then the message they are sending the message that VB shouldn't be used for long term development.
We as programmers/developers/system administrators need to stop playing ball with this upgrade mania. If you're building a website, no big deal, you'll probably completely redesign your site every few years anyway so you can sneak in an upgrade. But if your doing heavy lifiting, find something that's going to last.
Particularly funny for missing the boat is sound off. I agree with some of his assertions, but the parallel to the PDP-11 is just wrong. That's hardware; it wears out. Parts break, become harder to find, and at some point it becomes impossible to use. Software doesn't wear out; in fact, because it works, it gets more valuable as time goes on, and becomes more important to keep it running by whatever means necessary. The longer you can run on it, the cheaper it becomes. The tail end of its lifecycle is where it finally adds value.
What would you write a system in if you wanted it to last for 20 years?
This is Rob Meyer's weblog, a weblog focused on software development and system administration based on 10 years of experience. Want to explore further? You can find out more me or see the rest of my website.
Wondering if I've written on something in particular? Try searching:
You might want to take a look at some of the more requested postings (as judged by incoming traffic):
Want more? Subscribe to this site 
or contact me at rob at big dis dot com.
See my writings on: