eventjae.blogg.se

• #How to put files into a zip folder software#

They told everyone: “The API will break”. Which they should have anticipated pre-hand.

That is, if a plug-in was created for Maya 2011, it will not work with Maya 2016.” “You cannot load a plug-in for any version of Maya that predates or post-dates the version it was compiled for. I’m just gonna repeat myself: Autodesk breaks compatibility with every major version, on major applications like Maya. Companies that go bankrupt are the ones don’t care about their developer/user communities in this day and age, that’s not what happened. But nobody maintains it indefinitely.Īutodesk 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. Some companies value it more than others. Sure, you can maintain compatibility, but it costs money to do so.

There’s no “correct” way to program software.

#How to put files into a zip folder software#

Software that is correctly programmed doesn’t change at a fundamental level, it only becomes more complex. Python 3 is not compatible with Python 2, so all scripts would’ve had to been modified anyway. (usually just a re-compile, but still)īlender did a major rewrite going from 2.49 to 2.5, and they also switched from Python 2 to Python 3. In theory, you can create an interface using the C ABI, in practice they don’t give a shit and developers have to keep updating their plugins. You must not have seen a lot, Autodesk software breaks plugins with pretty much every major release, because they use C++ plugins and C++ compiler output is not binary-compatible across different compiler versions. The issue isn’t the compatibility itself, only the way Blender is updated, it is the only software I’ve ever seen that is incapable of maintaining compatibility with older plugins. I have years of experience working with graphic design, audio-design and mathematics that says otherwise. It is done this way precisely to avoid the issue of incompatibility, there is no reason to throw away hundreds of thousands of dollars, perhaps millions of dollars of work from various developers, it is simply not economical to not maintain compatibility. Software that is correctly programmed doesn’t change at a fundamental level with every update, it only becomes more complex, allowing it to use previousl plugins as well as new plugins, perhaps with occasional changes that switch on or off a select few source files and configuration files. The issue isn’t the compatibility itself, only the way Blender is updated, it is the only software I’ve ever seen that is incapable of maintaining compatibility with older plugins, ever. From all my experience in my years of working with graphic design, videography, audio-design and mathematics, I’ve never ever seen that to be the case. This is just a side note, but nobody maintains compatility with third-party plugins written for older versions of the software indefinitely.