02-12-2021, 11:31 PM
(02-12-2021, 04:25 PM)dhugg Wrote: wow,
its been a long time since i looked forward to going to a new release of software only to have the new version offer much less than the one being replaced (see windows 8)!!
i am hoping that my ignorance and lack of experience is the reason and that it can all be fixed.
i cant figure out for the life of me why anyone would design a new release that ignores all the hard work the users have put in to create expanded functionality through scripts. from a distance it looks like they purposely slightly renamed variables so that scripts we are all used to using don't work. i have gone through the effort of changing some of the scripts so they work for me but for the most part i find myself going to the old version 2.8 to complete a job because i need a script or two that they rendered useless??
i've read the release notes and while there is much improvement in the "inner workings" to the software what good is it if you end up removing functionality from the end product???
i also read where you can just "constantize" an old script and it will magically work but it never has for me yet!! after all if that was the case why didn't development just constantize each script before release... because it doesn't work!! i don't understand why people would waste their time in the future writing scripts if they understand that a new release makes them useless!!
i was a mainframe programmer for 30 years and i know that in all 30 of those years i would have lost my career if i did not consider, and plan for, a "transition" from the old software to the new often times called seamless.
i think it is important to realize that not every person using the software is a graphic artist specialist or programmer!
please tell me that i have something wrong so that i can apologize for being so negative but the end product is DISAPPOINTING as is!!!
thanks for listening,
dhugg
Yes, there has been some misses with some of the "constants" (while other "constants" have been handled correctly...).
I have also been close to mainframes in the 80s, and this is a part of IT where the fear of change is pervasive, nurtured by you-know-who to keep the customers in the ecosystem of the blue machines.
But well, 40 years later, they learned that they have to evolve or die. I'm currently working for the IT of a major bank and they have to move as fast as they can because a bank is only as good as its IT and their competitors won't wait for them. They are aware that some changes can be a bit disruptive but they will bite the bullet if necessary.
On the other hand, if your scripts don't work, it is also because they have lost their maintainers. It is one thing to use a script for a one-off, it is another to add the script to your permanent tool base without wondering who can do something if the script breaks.