* Powerful graphical tooling, where HTML/CSS are still catching up to
* Guarantee to actually have hardware acceleration, instead of CSS z-index tricks hoping for the best
* It was the first to support game engines on the Web, like Unreal
Unknown to many, Flash apps actually do exist on mobile, because Flash also AOT compiles to native code.
I don't think I've ever quite gotten over my resentment at the tech community for killing Flash in the name of "security".
So, most ads skipped to JS or gif animation, and most game developers rushed to develop for the app stores (where money could supposedly be made much more easily than on the web).
https://www.adobe.com/devnet/air/articles/ios-packaging-comp...
https://www.adobe.com/devnet/air/articles/ios-packaging-comp...
I personally miss the existence of thousands of Planetarion clones on the internet.
There is no miraculous contribution to open source 3D animation going on.
As a counterexample, I present: Homestar Runner. Also, Homestuck.
I don't understand why people keep repeating this. This is simply not true, Flash wasn't slow at all. It took HTML5+js+canvas years to catch up with Flash performance-wise.
Even after the introduction of GPU acceleration in browsers such as IE9 and Firefox 4, on typical machines of that period HTML5 was still far too slow for browser games, while Flash was usable even on Pentium III-era computers.
Obviously it was possible to code competent stuff with Flash; that kind of competence tended to be limited to few expert publishers.
Flash was performant in the sense that it allowed you to run decent graphical games at an acceptable framerate.
Flash was unperformant in the sense that it stole all of your computer resources to do it, and didn't play well with other elements on the page that needed those resources.
But GP is right that when canvas started getting pushed as an alternative to Flash, you just couldn't do as much with it. I remember seeing people online talk about how Flash could finally die, and then I'd load up the demo projects that they linked to, and they'd chug at 15 fps on my computer -- a computer that was more than capable of running a 30-60fps bullet hell flash game.
You have to remember that the game developer community's experience with Flash was, "you go to a page, full-screen my thing, and then play it." They weren't worried about how Flash interacted with the rest of the web, they just wanted good framerates and audio controls. The web developer community's experience with Flash was, "you go to my page, and suddenly everything slows down because Greg in marketing wanted to make a funny ball bounce around the side bar." They didn't care about whether canvas was hitting 60fps with hundreds of sprites, they just didn't want their webpages to freeze.
IMO, it's because flash was not great with resources, but good enough to try advanced/creative things. Sure, canvas wasn't even a common thing at the time, when flash supported many video/graphics use cases.
But that meant people thought a few effects on the website was worth including a flash animation which pegged your CPU at 100% for a while. Or auto played some FLV which killed performance for the entire website.
The performance was also very platform dependent. "Linux can support 128 cores, but can't play YouTube without stuttering." was a meme, but also the truth for many users for a long time. Then Adobe pretty much abandoned the plugin support on Linux.
So sure, the tech was great, and many people implemented it - maybe too many and too early.
The project's roadmap (https://github.com/ruffle-rs/ruffle/wiki/Roadmap) says: "The Flash Player has existed since 1996, and there are millions of pieces of Flash content around the web. This content represents an important piece of computing history and culture ... Ruffle's chief goal is to preserve this legacy content and keep it accessible for the future."
I think that's a good goal.
As for RAM and CPU usage, there's not much that can likely be done. Better garbage collectors and other things like that might help but Flash itself was the cause of a lot of those problems.
If this was a full implementation it'd be something open source that could run flash files/movies, so it'd be a bit less proprietary. There still wouldn't be open source editors that could handle doing it all so it wouldn't be complete or even close as an ecosystem.
That said, all this could end up creating a good alternative for when all the browsers and adobe drop flash support in the next year (Firefox ESR is the only one I know of that's committed to supporting it until the end of 2020). A sane and safe migration path would be really useful for somewhere like newgrounds or archive.org to preserve internet history.
• Proven track record of terrible security bugs
• Was most frequently used for ads
* Flash games market was huge
Regardless, that's whataboutery. Flash Player was famously riddled with security bugs. The question is [Browser + Flash Player] vs [Browser] and the answer is obvious. Removing an entire surface area—a pure subset—is always a security win.
My objection is only to people who in any way lament the death of Flash. Consider that nobody is scrambling to build a clone of the Netscape Navigator 4 parser and renderer. The fact that this project exists is testament to its importance for a brief period—but also to the awfulness of the canonical implementation.
Meanwhile, plenty of treasure has been found in the smoldering ashes of a dumpster fire. Rick Astley inspired an entirely new genre of comedy. That doesn’t speak to the inherent merit of his music.
And no, making “an app for that” is no replacement
So what? Flash created all sorts of usability problems. Horribly inefficient video playback, keyboard focus stealing, not responding to mouse/trackpad input the way native widgets do.
• Capability of ActionScript (which can harbor malware) along with potential vulnerabilities in the interpreter itself.
• Memory and CPU usage
• Proprietary
Does this rust variant even address all of these? Are we hoping to shim flash support into wasm-supported browsers? What good would this bring, specifically in regards to native flash's shortcomings?
Not trashing the project, cause it's actually really cool, just curious why.