To be honest, we're still pretty much on topic -- except maybe the part about command line inputs, VT terminals and punch cards. I'll give you that much.
But with any other upgrade offer, this one has to be measured against the ROI -- Return on Investment, or as I like to call it, the ROE -- Return on Expense since that's how it shows up in the company books unless you're the one who's actually selling the software.
And with the expense of purchasing the OS upgrade, you HAVE to factor in the expense of installing and maintaining it. That's why so many companies barely upgraded past Windows 2000. The bean counters simply don't see any reason to upgrade to a new operating system and potentially new computers when everything has already been fully tested and debugged on the current platform for years. Why spend money to fix something that isn't broke?
And then there's the cost of training the staff to use the new OS. Most people aren't computer experts. You simply can't dump something new on their desk and ask them to use it right away unless they're highly geeky IT professionals.
Then there's the big one: software that breaks under the new OS. And I've encountered that firsthand many times. I've had more than a few Windows APIs suddenly "change their behaviour" in my own software under Windows 7. But because I had access to the source code, I could fix it very quickly for my clients. But not everyone has that kind of access to an IT professional, especially with packaged software where you don't know on which continent the support department is located.
That's why the low price for Windows 8 is such a non-factor. It doesn't include both the costs and the penalties of performing the actual upgrade, something that's rarely discussed on any forum -- until now. And all because the new Metro interface has the potential to break a whole lot of software out there.
How much is that OS upgrade costing you now?