Flash is just a dying tech. Were someone to seamlessly roll its functionality into an easy to use package, I'm sure you'd see it die out for games as well, which is the only remaining use-case there isn't a ready replacement for.
At worst, they flat out lied to their developers and customers. At best, they are merely incompetent. Either way, if I were heavily invested in any Adobe technology I would seriously question how I could continue to trust that company.
However due to using the Adobe iOS tools(air etc.) The performance is dismal on iPad 2. iPad 1 owners have mostly sought refunds, and left bad reviews - forcing the developer to make the game "iPad 2 only" despite being a battery killing lap heater. (This already puts it in the apple cross-hairs as it's available to download to iPad 1 users.)
Discontinuing flash player is only half of Adobe's problem, the bad code is still being manufactured into processor-heavy apps which sap battery life and demand far-higher specs than what would normally be required if writing in native code, as noted in the example above.
The crux of the problem is that it's not a small amount of additional processing overhead, these basic apps are churning through battery via excessive cpu time.
These tools from Adobe are allow developers to port their flash games to the app store, and instead of increasing their revenue, it's creating problems and damaging their image/fan base.
"The memory limitations of iPad 1 (which are somewhere around 115 MB RAM per app) are just quite challenging. You have to have it running around 80-90 to keep it stable and the app has tons of timeline animations, the sources are 1 GB, all compiled into one single SWF file + some assets. The app was originally made for PC and upgraded for tablet devices. When you start creating tablet apps from scratch it's a whole different story. The game is now made with 'no compromises' compared to the desktop version and that keeps it unique."
The worst part being it is so even for trivial flash objects like those "copy to clipboard" clicky thingies (e.g github). It was not skyrocketing to 1.0 loads but enough to prevent the CPU to go in some deep C-state mode and/or back off frequency or whatever. Having such a NOOP Flash object was literally removing in order of hours from my battery life ("was", because ClickToFlash is brilliant).
I guess that way they will be true to their promise: the next iteration of Flash for Mobile will, in a way, be both stable and a non-battery sucker.
I gotta call BS on that. I've personally played hundreds if not thousands of flash games on an under-powered $500 laptop purchased in 2009. The article itself mentioned the success of flash on Blackberry devices, due largely to the fact that they cooperated with Adobe's engineers instead of freezing them out.
That's like the overstatement of the year...