https://github.com/ruffle-rs/ruffle
If Adobe had seen their ban from the iPhone as a challenge to make Flash player capable of running without a plug-in they would dominate so many areas today. Flex would have become a viable platform to develop web apps/PWAs with - effectively sitting in the same position as what Flutter is doing today (Although I don’t believe Flutter is a one size fits all universal toolkit). I suppose they tried with PhoneGap but without Flash/Flex, which was their super power, they just didn’t have enough value proposition.
I suspect they saw the desktop install base of Flash Player as too important to risk loosing by marking it redundant - innovator's dilemma.
For some reason they just excepted defeat with Flash.
I think WebAssembly is the most natural fit here.
And even if it's the same amount, having a sandbox that's harder to escape, holding everything else equal, seems like a win for end-users.
Flash's demise, while it caused me no end of grief back in the day as it was the bulk of my income, was a good thing in the end.
I remember reading examples from an e-book on how to build 3D scenes with Flex 3 when I was 17-18 years old. It was a short lived dream of mine to create online video games. Instead, I ended-up making add-ons for PHP-based forums.
During that era Unity had its own web browser plugin and there was at least one Tennis-like game on the miniclip site itself.
Who's checking for this stuff on every blog page open, actually? I wish I was, but, usually am not.
Flash suffered from not having a spec other than its implementation. Made it hard to fix bugs while being backwards compatible
I’m not counting ad tech and the various user-hostile websites because they’d have happened in Flash too (rather, Flash ads were already a thing too)