I just need to be sure that they are not going to some how stop everyone who has X-8 from using it if you do not pay the $199.00 dollars first.
Right off hand, they can take the activation server offline.
Or, a version of Windows 3 yrs down the line isn't able to install X8 or it breaks the current install of X8 (via the wonderful update system that Windows has in their wonderful rolling release, always in Beta OS) to where you have to use one of your finite activations to get it installed back again.
Or you use up all your activations through the natural course of swapping out computers or having it installed on more then one at a time etc.
I'm sure I'm missing a few that they can do as well with a little creativity, but all of which would be permissible due to the terms of the EULA (again, why I always bitch and moan about people knowing their EULA).
The Adobe stuff (unfortunately) seems like a necessary evil whether one likes Adobe or not.
I think that is the key phrase right there. How much of this is truly a need over what people
think is a need. There are certain pipelines(workflows) to where I can see it as a true need, but then in some cases, it's more of a mental thing that people think that they need it.
And it's being objective in that regard.
My standards on what constitutes a successful .AI file import operation is probably quite a lot more strict than what others are willing to accept.
I think it all depends on what you can do with it after that import as well. I've got plenty of tools that provide me with a successful
visual import and that's all that I need. If a design had any gradients or blends or gradient meshes in it, my production programs couldn't accept it as vector files anyway as those elements would throw it for a loop.
I also don't need a vector file at all, to do what I do. Which is a good thing, about 97% of my customer supplied files are raster files (even directly from the designers, including ones from here). With my own designs that I create from concept, I'm skipping the vector stage in a lot of the instances and working right from sketches.
This isn't everyone, situations will vary, I would just caution to be honest and evaluate what ones needs truly are if this is rattling your cage in the slightest.
Bare in mind, workflows will take a hit as relearning how to achieve what effect may be different in the newly acquired software package.
People need to be honest what what they truly need and what they only think that they need. With software like this, things typically only get more restrictive, not less, just keep that in mind.