I call a bit of BS about this. In the end, the code that creates js or HTML5 equivalent (poorer versions in fact) end up being far more resource intensive and buggy than flash was. Importantly, this is after millions of man hours were put into optimising the hell out of the js engines. Further, apple itself ended up optimising it's processor architecture to allow faster JS execution.
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.
> In the end, the code that creates js or HTML5 equivalent (poorer versions in fact) end up being far more resource intensive and buggy than flash was.
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.
Do you not recall that flash was a the worst of the closed source rubbish.
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!
Never really thought about what a blessing Electron is for Linux users. Electron means Linux Desktop users are a build away rather so they get the same resource hogging apps Windows and Mac users do.
My experience was that Flash ran like garbage on anything but Windows/Intel. Linux/Intel? Trash. Mac/PPC? Trash. The web at the time was unusable on my PowerBook G4 without FlashBlock. Maybe Flash would still be around if Adobe bothered to make it run well on anything but one platform.
I worked at a creative studio that used Linux during that time. For many periods of time there literally was no solution for doing something as trivial as watching YouTube videos (a huge need for reference) because of trying to pin down the right combination of 32/64 bit OS, browser, and Flash plugin.
i remember cheering apple on as they were killing flash because of how abysmal it was on linux. I do miss flash in a way, but also good fucking riddance
> Flash was fundamentally to resource intensive for mobile and arguably still is.
Flash run on PC's hundreds of times less powerful than your smartphone is right now. For the original iPhone, sure, but this resource argument is decades out of date now.
In the years after, all we've done is made HTML/JS/SWF as powerful as Flash and even more resource intensive.
The one ultimately responsible for Flash's death was Adobe, who neither felt it was worth investing in to overcome these issues, nor worth open sourcing to let the community give it a try.
That doesn't mean anything, Adobe has added support for everything to PDF. Adobe wanted (and tried hard for a while) to make PDF the defacto way to use the web. Instead of authoring HTML you'd publish PDFs. Links would take you to other PDFs within Acrobat Reader. Acrobat Reader was the browser they wanted people to use, before anyone knew what a browser was. So, they had to have Acrobat Reader support all of those content types.
For Adobe I give full marks for cajoñes and long term thinking, but I'm gonna have to deduct points for the closed nature of it all.
Jobs didn't like Flash because it was a potential escape from the walled garden. I have my issues with Flash, but Jobs' reasoning was purely business model.
It is always difficult to try and second guess decisions which were made by other people behind closed doors. Particularly when you know the end outcome where the people who made the choices wouldn't have.
When Jobs wrote that memo, the iPhone wasn't remotely dominant. It had tiny market share on and Windows Mobile and Android were both very big threats to the iPhone. There could easily be an alternative history where Adobe wrote a really effective version of Flash and Apple was left out in the cold.
Fast forward 10 years and it all looks obvious, but I don't think it was a slam dunk back then.
But Jobs was also right, Flash was fundamentally to resource intensive for mobile and arguably still is. Without mobile, Flash was doomed.
Flash also has a bunch of other issues in terms of security and performance on PCs which were never really addressed.