https://upload.wikimedia.org/wikipedia/commons/9/9b/SMIL_mis... missile command clone
https://upload.wikimedia.org/wikipedia/commons/1/13/London_U... tube map
https://upload.wikimedia.org/wikipedia/commons/4/49/Rolling_... rolling shutter animation
https://upload.wikimedia.org/wikipedia/commons/9/9b/SMIL_mis... missile command clone
https://upload.wikimedia.org/wikipedia/commons/1/13/London_U... tube map
https://upload.wikimedia.org/wikipedia/commons/4/49/Rolling_... rolling shutter animation
As for the first link, I immediately had to come up with a way to click on the warheads programmatically. I saved the world! :D
You could pack so much into a single binary distributable media file. Games, videos, websites, infographics, tools, chat rooms.
SWF was brilliant and it should have thrived.
Also they were basically the founders of persistent fingerprinting via Flash cookies.
So no, thank you, I'm more than happy it didn't thrive more than it already did.
I was thinking that might be a useful thing for people to spot when a ToS, EULA, etc. changed since those are long documents that frequently get sneaky revisions.
This is 570k and runs in a webassembly runtime:
https://archive.org/details/flash_badger
SVG could do that too. Minimal javascript plus audio tags.
http://xn--dahlstrm-t4a.net/svg/audio/html5-audio-in-svg.svg
yes stuff like that & the IOSYS MVs. you technically can do stuff like that today theres nothing stopping you from doing it with svgs but i meant more the social part of it. its just interesting that if you want to do the same thing (put an animated video on the inernet) the usual way its now 10x bigger yet looks worse.
also i dont think theres anything like Flash (the authoring software) but for SVGs. i hope there is one but for now I wouldnt say inkscape + a text editor counts
(It observes that this feature raises certain security risks, but promises to figure out by the next draft how to fix them. This of course never happened.)
I recall Hixie had a funny rant about this, but I can't find it.
IMO the fact that it belonged to Adobe was the biggest problem, if SWF had been managed by a more capable software org it could have been maintained in a way that kept it from getting banned from the internet. And remember, that's how bad it was - it got banned from the internet because it was absolutely indefensible to leave it around. SWF getting cancelled magically stopped every single family member I have from calling me with weird viruses and corruption they managed to stumble into. I saw more malicious code execution through SWF than I saw from my dumb little cousins torrenting sus ROMs and photoshop crackers. I'd rather not have it than have those problems persist.
I bought Flash once. I found a crashing bug and jumped through hoops reporting it. A year or so later, they updated the ticket to suggest I drop $800 for the privilege of seeing whether it had been fixed. I did not make the mistake of giving them money ever again.
They had such an opportunity to take advantage of a platform with a pre-iPhone deployment in the high 90% range, and they just skimped it into oblivion. What a disgrace for everyone who actually cared.
Obviously the fact that it was that low-friction to install any non-sandboxed application code was a very naïve thing to allow, but I still have to hand it to the Macromedia developers for packing the whole player into such a tiny download and making it so frictionless. I'm pretty sure that had a HUGE impact on its adoption over say, Java applets. Java took a lot more time and effort to install, and while it had decent penetration (many "chat room" services and in-browser games like Yahoo Games used Java) it was never taken for granted that 'everyone has it' the way Flash was (until Steve Jobs singlehandedly burned that assumption to the ground with fire).