Ruffle – A Flash Player emulator written in Rust
41–50 of 94 posts
Re: Ruffle – A Flash Player emulator written in Rust
#42Those sample files.. bring back memories. I think we took a step backwards in serving vector art/animation on the web. When YouTube replaced Flash, we've probably wasted petabytes of bandwidth serving rasterized content when Flash or a similar format would have been much more effective.
Re: Ruffle – A Flash Player emulator written in Rust
#43A FOSS Flash Player implementation has certainly value, and I hope to have contributed to the cause by starting the Lightspark project years ago. The sad reality is that the Flash runtime is massive and under-documented. The best approach for Flash preservation in the medium term is using _actual emulation_ to run the binary player itself. Further reading: https://medium.com/leaningtech/preserving-flash-content-with.…
So, to archive/preserve content that was lost because it relied on a proprietary closed-source technology we should be relying on _your_ proprietary closed-source technology? Please. I understand you're trying to make a living here, but being able to use F/LOSS software is absolutely critical for the preservation movement. “Not-for-profit, charitable and educational organisations can benefit from discounted rates.”.…
Re: Ruffle – A Flash Player emulator written in Rust
#44A FOSS Flash Player implementation has certainly value, and I hope to have contributed to the cause by starting the Lightspark project years ago. The sad reality is that the Flash runtime is massive and under-documented. The best approach for Flash preservation in the medium term is using _actual emulation_ to run the binary player itself. Further reading: https://medium.com/leaningtech/preserving-flash-content-with.…
I see you over and over again in Flash Player threads. Your approach isn't good because it requires someone else's, namely Adobe's, cooperation, and even then, you still end up with a black box inside another black box. Doesn't feel sustainable.
Re: Ruffle – A Flash Player emulator written in Rust
#45Earlier quoted context omitted.
I see you over and over again in Flash Player threads. Your approach isn't good because it requires someone else's, namely Adobe's, cooperation, and even then, you still end up with a black box inside another black box. Doesn't feel sustainable.
Why does it require Adobe's cooperation?
Re: Ruffle – A Flash Player emulator written in Rust
#46Earlier quoted context omitted.
I see you over and over again in Flash Player threads. Your approach isn't good because it requires someone else's, namely Adobe's, cooperation, and even then, you still end up with a black box inside another black box. Doesn't feel sustainable.
Why does it require Adobe's cooperation?
Re: Ruffle – A Flash Player emulator written in Rust
#47Earlier quoted context omitted.
I see you over and over again in Flash Player threads. Your approach isn't good because it requires someone else's, namely Adobe's, cooperation, and even then, you still end up with a black box inside another black box. Doesn't feel sustainable.
Why does it require Adobe's cooperation?
https://medium.com/leaningtech/cheerpx-for-flash-now-general...
Re: Ruffle – A Flash Player emulator written in Rust
#48Re: Ruffle – A Flash Player emulator written in Rust
#49Adobe already released the universal activation keys cause they shutdown the servers but it's still not legal to use if you haven't bought an original copy https://helpx.adobe.com/x-productkb/policy-pricing/macromedi...
Re: Ruffle – A Flash Player emulator written in Rust
#50Those sample files.. bring back memories. I think we took a step backwards in serving vector art/animation on the web. When YouTube replaced Flash, we've probably wasted petabytes of bandwidth serving rasterized content when Flash or a similar format would have been much more effective.
SVG is much better at vector art use cases. Flash was horrible from user pov (constant os and browser compatibility problems, unending stream of weekly "ads can pwn your computer" level security holes, proprietary black box nature, ate your battery, hard to procedurally generate, didn't integrate with the web and dom, etc etc).