hugo This maybe a new unnecessary FUD.
What are you talking about?
hugo We already had this before and there is no proof and it's the same scenario.
When did we have something like this before? Who else was asking for these features/bugs to be fixed?
hugo Do you expect that Adobe inform that will abandon AIR ?
Adobe already abandon AIR, now its too late for any info.
hugo It was really a surprise for you that happen ?
Yes it was. The way that they do it. It was an actual surprise.
hugo If that game it's so important and the performance it's a major concern, than on my opinion, you should search for alternatives more focus on mobile and performance.
Woow, this is such a smart advice. I wonder how I did not remembered this. Lets just rewrite 200 000 lines of code overnight and retest everything. Problem solved!
hugo AIR it's a great runtime and very generic but it's not mobile optimized.
So what? Does that means it shouldn't be. And for what is AIR optimized. Is AIR optimized for any platform specifically. Is there any platform where AIR does not have major performance bug? I will give you 3 platforms:
1) Terrible GPU memory leak in Windows 10 using DirectX 11.
2) Terrible memory allocation (thus triggering GC more often) on iOS when using Vectors of non primitive types. Also getTimer function triggers allocation.
3) Context3D.clear() method terrible performance on Android.
So as you can see AIR is not optimized for any platform really. But it is very close to be and that is why I am asking from Harman fix this problems. And what do you do? Instead of supporting me you write this stupid responses that I am spreading FUD, really? Wouldn't be much better if you wrote reply of support something like hey yes this would be useful please Harman fix/implement this. Instead you are trying to silence people and that has no actual value really.