We’re talking about software compatibility, you’re resorting to comparisons of murder and white supremacism. How am I even supposed to take you seriously?
Does not follow. A majority consensus does not logically mean actions against it are impossible. Do you think most people want plugins to constantly become outdated? They don’t, but it’s an equilibrium between how much people want newer software and how much people want to avoid the cost of making a large change.
That’s not the point at all. Here’s your claim:
“Autodesk had one major change that made a lot of people mad as it lead to many smaller changes, but they did it for security and integrity reasons and it was intentional, it was planned.”
This is factually wrong, I’ve shown it to be wrong, that’s all I set out to do. I don’t like it, either.
But that’s mainly a concern for the compiler, a majority of software built from C++ continues to function and furthermore autodesk wanted it to be this way, it makes their up-to-date software more secure which is a concern of theirs.
Using a newer compiler doesn’t generally make your software more secure, security-related compiler bugs are very rare.
As I said, it is entirely possible to create a plugin API that doesn’t rely on C++ ABI compatibility, it’s just more work and Autodesk just doesn’t care enough about plugins not breaking.
But they would be guaranteed to predict it if what you were saying is true, that everything always breaks all the time.
I’m not saying everything always breaks all the time, I’m saying something breaks all the time. Sure, they could’ve predicted that something will break, but that’s a pretty useless prediction.
In fact, the Python3 breakage was highly controversial and it’s a problem to this day, lots of projects never switched. I’d be the first to argue it shouldn’t have happened, but it happened.
Not how much extra work would it have been, but how much extra work would it have saved? If it’s too expensive to make a change, then your software is just dead in the water, you won’t have the budget to update it and fix bugs. The more work you put into dealing with the future, the less work you need when it arrives.
I can’t stress this point enough: You have no idea how software development works.
If I break compatibility, it saves me work, right away and indefinitely into the future. It may create work for other people, but I’m not paying for that. I have to choose the balance between pissing them off and maintaining my flexibility to make changes. Furthermore, the more you plan for an inevitably uncertain future, the more you will be wrong when it actually arrives.
A majority of users will choose new script so long as it does not impact their previous capabilities. I garuntee you if blender released some new version where their animation plugins were the best of their kind in the world but all modeling plugins were disabled, blender would just die out or at the very least it wouldn’t be anywhere near as popular as it is now. Even maya, which is primarily chosen for animating, still has many modeling and texturing abilities that allow you to consistently work with adjusting 3D animations.
What actually happens is that Blender developers make some change, some scripts break and then scripts are updated, unless they’re not actively developed anymore. If they’re not actively developed, it’s the scripts that die out, not Blender. This happens all the time. Again, not saying I like it, but that’s how it works.
Google sure doesn’t after I gave them money to be my render farm, no thanks to you by the way, you’re clearly just here to waste everyone’s time instead of finding solutions.
I’m talking about the actual customer support people dealing with you. Does Google even have customer support? Did you ever contact them?
Then that would have to mean it’s not for a majority of users, so I guess you’re saying to get ready for blender foundation to go bankrupt, not that I don’t have several other 3D softwares anyway.
I’m talking about the Azure script. It’s clearly not for you and I won’t give you support for using it. Maybe Blender isn’t for you, either.