A retrospective on a nearly 25-year history of Flash, as Adobe prepares to officially end support and distribution of Flash Player in December 2020
Before Flash Player sunsets this December, we talk its legacy with those who built it. — Few technologies have yielded such divisive and widespread passion as Flash. Tweets: @wiredcoach , @john_m_nelson , @stealthpuppy , @lifeandtimesvg , @jonyiveparody , and @changeist Tweets: Charlie Jackson / @wiredcoach : Detailed article by an incredible writer. There were already 187 comments. Many said good riddance, which made me chuckle. Some ripped @Adobe. My favorite was that Flash didn't last very long. Say what? Almost 25 years in the tech space is an eternity. https://arstechnica.com/... John Nelson / @john_m_nelson : Ah Flash. Whatever its faults, it let a non-programmer like me make fully interactive maps and websites. https://arstechnica.com/... Aaron Parker / @stealthpuppy : The rise and fall of Adobe Flash https://arstechnica.com/... “Before Flash Player sunsets this December, we talk its legacy with those who built it.” https://twitter.com/... @lifeandtimesvg : I suspect lots of folks following me here will dig my latest freelance feature, on the rise and fall of Flash — featuring input from two of its creators and four others who contributed in some way to its growth. https://arstechnica.com/... @jonyiveparody : A great writeup of the world's worst Internet plugin. https://twitter.com/... @changeist : Misread this as Adobe Flesh and then had a horrible premonition. https://twitter.com/...
Context & Ripple Effects
The arc here runs long: Adobe announced back in 2017 it would stop updating and distributing Flash at the end of 2020 (the three-year sunset notice), giving the ecosystem time to migrate. Even before that, archivists were already scrambling to preserve Flash sites as usage collapsed (the 2015 preservation scramble) — so by the time this retrospective lands, the question of who saves what had a five-year head start.
Why it matters now: the retrospective arrives months before the December cutoff and ahead of the hard enforcement — browsers blocking Flash content and Adobe starting to kill playback itself in January. The post-mortem debate is already visible in the follow-on coverage, where developers argue the promised replacement never arrived as an accessible authoring environment.
First-order effects
- Content built on Flash loses its default playback path once major browsers block Flash content from January 1 and Adobe starts blocking from January 12 — site owners and game developers who never migrated are cut off regardless of whether their content still works technically.
Second-order effects
- The replacement stack takes heat immediately: developer threads argue HTML5/JS remains 'in the stone age' as a newbie-friendly animation and graphics authoring toolset (the post-sunset critique), meaning the creative-tools market Adobe vacates at the low end is not cleanly absorbed.
Third-order effects
- If the pattern holds, browser vendors and runtime owners — not standards bodies or creators — decide which web technologies reach end of life, making coordinated platform-level kill switches the template for retiring legacy runtimes; meanwhile, institutional archives rather than living links become the durable record of a generation of web media.
The trend: Web platforms are consolidating authority over runtime lifecycles — a single vendor decision plus synchronized browser blocks can retire a technology that defined two decades of interactive media.