So what was he supposed to do? There was no upgrade path or migration plan 5 years ago either.
This is why my dad still uses Appleworks. I said the same thing to him 5 years ago: "Upgrade!"
He said "Sure, help me do it." Every solution I found would have taken hours and hours of work to manually re-make his databases so I gave up and told him to keep using Appleworks.
Now we're having to do all that this year, but whatever. It's the same amount of work now as it would have been back then, so why does it matter when we do it? There is no "upgrade path."
Then there needs to be a migration plan, even if it's as colossally ugly as doing things manually, or hiring a consultant to assist in the migration. I'm not saying it's pleasant, but having worked in IT for several years, to me it's completely dumb to run a business on something that's been EOL'd for nearly 5 years, and have not already been greatly working on a plan.
Developers have to re-write code when things change so drastically that they can't use existing platforms. Committees decide to discard previous infrastructure and force IT to start from scratch. Stuff happens all the time like this. The point is,
if it's for a professional business, you've got to have already thought of this, or hire someone to think of it for you, otherwise you end up in ugly situations like this.
It's not like Apple is the first company to do something like this.
However, this is a pretty bad blunder for Apple.
