42 ms·
Someone I know worked on flash at adobe. Long before it was "dead" it was "dead". What killed it? According to my acquaintance it was Apple. Apple disallowed
by cogman10 4y ago
Someone I know worked on flash at adobe. Long before it was "dead" it was "dead". What killed it? According to my acquaintance it was Apple. Apple disallowed flash on iOS which adobe was counting on as being a big expansion of the flash market.
As for the dev environment around flash, according to them it was a nightmare codebase not for the faint of heart. It isn't surprising that adobe decided not to port it to WASM because it was a spaghetti mess.
There's a reason Flash was often a virus vector back in the day.
- IshKebab 4y agoApple definitely accelerated the process a lot, but Flash on Android was abysmal so I think people would have moved away from it eventually anyway.
- jaywalk 4y agoSame with Flash on Windows Mobile before it. Even if Apple allowed it (and I shudder to imagine an alternate timeline where they did) I doubt Adobe could have made it much better.
- titzer 4y agoI've heard similar anecdotes about the VM being a mess. Where Adobe seems to have royally screwed up is creating an unambiguous specification for SWF format, and also disallowing other implementations of SWF. Instead, they become beholden to a codebase that no one could make heads or tails of, with no way of creating a clean rewrite that was guaranteed to replicate the behavior. In designing Wasm we were very conscious of this, which is why Wasm has a very, very explicit specification that is simple with only the minimum non-determinism (some NaN issues) and no UB.
- masklinn 4y ago> What killed it? According to my acquaintance it was Apple. It was definitely what drew the first blood. But in fairness, a lot of people were crying for blood, flash had issues all over, and it was a complete security disaster. Apple's decision basically gave everyone the OK to dump on it. It also happened at a time where the idea of open web was ascendent, MSIE was being actively fought against, and the people involved were out to excise proprietary platforms. Also all mobile platform flash implementations had been absolutely awful, barely usable battery killer even ignoring that the UI affordances were just not adapted for mobile touchscreen devices.
- josefresco 4y ago> It was definitely what drew the first blood. Lack of iOS compatibility was the nail in the coffin. Our web agency already hated Flash because it lacked any SEO capability, and the editor was shit. When the iPhone dropped it we had already been building websites without it for a couple of years. It was just a nice accelerator and allowed us to deny clients who requested Flash much easier. Fast forward a couple more years and security became the main issue. Many of our clients were infatuated with their Flash websites and didn't want to move on. I just took down a Flash website (replaced with HTML/CSS/JS) in... 2022!
- phire 4y agoIt might not be quite correct to describe it as the final nail in the coffin, but it absolutely was the killing blow. Flash had been on shaky grounds for years. It was obvious that it had a limited lifespan, and that it eventually needed to die. I think even Adobe recognised this. But Apple accelerated it's death massively, and everyone seems to be very thankful for that.
- deckard1 4y agopeople that romanticize Flash are selectively remembering the cool uses such as Newgrounds and Homestar Runner. They are forgetting Flash ads, which were stuffed on a page to the point they would crash your browser. Or the constant fun of hunt-the-talking-banner. You could always tell when you landed on one of these pages by how fast your CPU fans started spinning. If your PC sounds like a jet engine, you're on a heavy Flash site and should close your browser ASAP.
- pjmlp 4y agoNow they get ads using WebAssembly and WebGL instead, what an improvement!
- egfx 4y agoIt’s not just about AlbinoBlacksheep and NewGrounds. Flash was the most consequential technology on the web’s frontend prior to and even after html5. It was enabled on a staggering 98% of web browsers. So much so it was basically synonymous with web browsing. You can trace the trail of flash to the invention and adoption of social media. There would be no MySpace, no YouTube and Meebo. The internet would have had a completely different story.
- irrational 4y agoIt was definitely Apple from my perspective. We had this amazing training site built in flash. I’m taking full on animated storylines, professional voice talent, everything. Our animation teams were releasing new content every three months with new product seasonal launches. We won lots of awards. Then… Apple launched the iPad. All of our retail partners announced they were going to adopt the iPad to train sales associates. And the iPad doesn’t run flash. Well… crap. We laid off the animation teams and told the voice talent there would be no more work. All of the content switched to plain plain html - text and static images. So boring. We saw massive drop in usage, especially in Asia where they lived the animated stories (the flash animations were translated into 40 languages). It has been 10+ years now and the site is around, but it is still boring plain text and static images. Flash had problems, but it was also something really special that has not been replicated since Apple killed it.
- auggierose 4y agoSo it was deemed too expensive or risky to just turn it into an app? Sounds like you had your business model already figured out, building the app sounds like the easy part.
- irrational 4y agoFlash file sizes were very small (they were basically just vector graphics). We tried making them into videos, but the file sizes, even greatly compressed, were too big for our Asian retailers. This was in the days before video streaming really came into its own. If we were making the decision in 2022, we probably would have gone with videos.
- JoeyJoJoJr 4y agoThere was never any simple way of turning it into an app with these sort of products. Flash had a very unique set of functional/creative affordances that have never since been replicated in an authoring tool. I worked on many bespoke solutions to migrate Flash animations to apps and the lack of proper integration and ecosystem supporting the workflows made it far too impractical to try and reproduce much of Flash’s functionality. It many instances the business objectives were tied directly to the capabilities of Flash. Flash also had an extremely robust means of loading isolated application modules that helped businesses isolate their workloads and scale their applications. Solving that problem once Flash was gone was beyond the capabilities of many businesses that relied heavily on Flash.
- strangattractor 4y agoIn addition Flash was a battery killer if my memory does not fail me.
- yardie 4y agoOkay but Android phones of that era did support Flash and it was one of the advantages Android had at the time (Motorola Droid era) that they were advertising heavily. The iPhone doesn't support Flash, Android does. Therefore you want an Android phone to access Flash content.
- monocasa 4y agoI had flash on a Motorola Droid and it was awful. Not only did the VM have questionable compatibility for some reason, it also completely destroyed battery life. Cute trick, but not really usable for day to day.
- dataangel 4y ago> It isn't surprising that adobe decided not to port it to WASM because it was a spaghetti mess. Business people never use this as part of the decision making process. If there's a market they will throw programmers at it and ignore their warnings.
- cogman10 4y agoBusiness people don't know WTF a WASM is. I'm sure "we should get flash mobile" was pitched at one point in time and the "we'd have to rewrite everything in Javascript" was ultimately what killed those sorts of notions. Because, business people care that "this will be a multimillion dollar investment"
- mind-blight 4y agoI was a contractor at the time of that announcement, and I remember using Apple's announcement as leverage to convince a customer to fund migrating their learning app from flash to html/JavaScript. Given how difficult it was to maintain a flash codebase well with multiple developers jumping in and out of the project, we pushed that angle pretty hard
- moralestapia 4y ago>According to my acquaintance it was Apple. LOL, that's far from insider info. Steve Jobs publicly said several times that he was going to kill Flash. And he did. And the reason for that wasn't "Flash is an insecure platform". Flash was in the way of a thing called the "App Store" which, fast forward to 2022, has made Apple somewhere around a trillion (with a t) dollars.
- Terretta 4y agoAt the time, iphone was initially intended as platform for HTML5 apps, which it can still do today. So less about App Store, more about a number of dimensions of usability. Devs demanded native apps, not Jobs. The problem with Flash was that it was a grossly inefficient runtime for arbitrary code with security issues, an extreme battery hog, and had no affordances for touch (e.g. you couldn't 'hover'). As I recall, battery was the biggest problem, security close second, UX inconsistency third, and runtime for arbitrary code (still disallowed!) as nail in coffin.
- deadbolt 4y ago> LOL, that's far from insider info. Steve Jobs publicly said several times that he was going to kill Flash. And he did. This is one of the first things which makes me feel old. "heard it from an aquantance" shit we all saw it happen! I wonder if people are to young to remember it, or maybe there are a lot of people who just don't remember it at all.
- moralestapia 4y agoMy thoughts as well! We old school now :D