I doubt it. Adobe tried to make a go with Flash on Android to spite Jobs and it was a train-wreck. While Android makers were willing to put giant batteries in to support sloppy code, Apple wasn't.
> The iPhone might have taken a few more iterations, but eventually they would have figured out how to support flash well in their phones.
Apple shipped a phone with barely a day's battery life and it remained that way for years as features and performance caught up. If they'd shipped Flash, it would have cooked the CPU on every site it visited ruining the limited battery life the phone had. This is one of those cases where shipping less made a better product.
> In the end, the reality is that Jobs made a tech forecasting mistake assuming HTML5 (not js) will eventually catch up with flash.
You are splitting hairs. Nobody has made a perfect technology prediction 10 years out.
It never played well on any system I cared to use. The tools to generate it were unavailable to the likes of me and a lot of people here, who back in the day were second class citizens.
Also it tried to make the the Web TV before there was anywhere enough processing power at the ends nor bandwidth in the middle.
Designers on their expensive powerful machines built magnificent content that nobody who respected the technology in their personal stack, and paid a reasonable price for their infrastructure could use.
Well, back in the day we may have been second class citizens. How the world has changed. Good riddance to bad rubbish!
What would have happened if Steve Jobs hadn't made an ultimatum on Flash? The iPhone might have taken a few more iterations, but eventually they would have figured out how to support flash well in their phones. We might even be in a place where processors are designed to efficiently execute flash (the new M1 has so many specialization this is not even reaching out).
Instead what we have today is a mess of things that still don't add up to technology we had a decade back, and we have really bad, inefficient code running everywhere trying their best to emulate what flash did.
In the end, the reality is that Jobs made a tech forecasting mistake assuming HTML5 (not js) will eventually catch up with flash. It never did. As poor forecasting decisions go this is fairly reasonable, but we cannot move forward if we continue insisting that this was the best decision even in retrospect.