I’m not saying it makes a ton of sense. I’m just saying thats how people feel.
The problems that exist in older releases become a known quantity after a period of time. People come up with workarounds and tricks for addressing the issues. They learn about the issues from colleagues and they try to stay on a release which is generally regarded to have fewer issues.
What they’re afraid of is moving to a new version where the current issues are entirely unknown and liable to bite them in the ass right as they try to deliver a job.
I’m not claiming that there is some great marginalized community of Flame artists. We’re all doing pretty well as far as I can tell. That said, inclusion is about meeting people where they are and not about asking them to come to you.
If we know that the vast majority of Flame users aren’t interested in engaging with Autodesk, the onus is on Autodesk to fix that, not the users. If it is known that there is a legacy feeling of distrust lingering in the community then it seems like it would behoove Autodesk to do something about it.
We’re a superstitious lot and that superstition is born in large part from not understanding how the software works on a fundamental level and repeatedly ending up in situations where we feel entirely beholden to the unknown and seemingly capricious whims of a software which forms the basis of our livelihoods.