| ▲ | MattRix 4 hours ago | |
This take doesn’t make sense unless you’re comparing Flash to current technology, rather than the tech of its time. It’s like saying CD players were awful: sure they’re awful NOW, but they had a time and a place when they were the coolest thing around. Similarly, the only reason Flash had “bad performance” on low end devices is because people were using it to do stuff that web tech could not do. It took over a decade for web tech to catch up, and 20 years later we still don’t have tooling that’s as good as Flash was (other than Adobe Animate itself). Calling it “terrible for video” is completely backwards! Flash became the standard for video on the web for years because everything else was terrible and Flash was the only thing that worked. There’s a reason that YouTube used Flash to play videos for the first ten years. | ||
| ▲ | larusso an hour ago | parent [-] | |
It’s one of the topics I feel I’m too biased since I spend 10 years as a flash developer. The requests for widgets and or small applications we got where simply impossible to write in a frontend only fashion at the time. And a lot of my peers moved on to work on HTML5 which was pushed hard as the successor at the time. A lot felt like a step back. I moved to native iOS and worked on games in cocoa 2D. I remember that I thought more than once: “This was already solved in flash”. But I think in the end it’s a good thing that we don’t have or need the flash player anymore. I wish only we could have gotten a flash to wasm/webgl compiler or flash to js transpiler. ActionScript 3 was great and leagues ahead of JavaScript at the time. | ||