WildWestDesigns
Active Member
I know all to well the teething pains, no only did I switch programs, but OS as well (and to one that doesn't even have 5% of the desktop market share). Not only that, but have written some of my own in house tooling (and I by no means have the same amount of resources that some companies, even on here, have). However, most people don't consider what it's going to cost them sticking with it especially long term (now if close to retirement etc, so what).That's exactly why people don't switch. They generally started with a particular software or system for ease and compatibility and it becomes entrenched in their operation. Then when people are reliant on it, like with illustrator, they change the terms so you either deal with it or are forced to make a slow and costly changeover to something else.
I don't think people make an honest assessment of the C/B of it all and I have seen some (on here) that try to look at alternatives, I'll see them claim that some things (functionality) don't exist, I'll mention how to do it and they will go "I don't like that way, so it may as well not exist". That's fine, but I have little sympathy when they get raked over the coals.
Companies aren't going to change unless one uses their wallet to let them know. Still paying the monthly fee and grousing isn't going to do much, they have your money.
As to Google, I have seen way to many times Google kill something even if it was a hot item. I wouldn't trust them for anything that I truly was dependent on. I don't even trust them that much to use Go for some stuff and I kinda like it (GC aside), but I digress.
More and more, I'm glad that I never was entrenched in program specific workflows and when I did teach people, I always did it in the more program agnostic way. I grew up still doing things manually and even with software, I still like doing that.