The design philosophy behind flash was to let you make animations and interactive content.
The design philosophy behind html/css/js/web stack is a composable system of modules that can be bundled, used to center objects, and plumb state to components.
Flash was on another level. The web hasn't been the same since it left us.
But ignoring all of that, here's a quick list of (some) categories of things I still miss from Flash:
- nested animations/clips: The recursive nature of Flash made making animations very fast. It also opened up some workflows with AS2 that were not particularly scalable, but that were excellent for fast prototyping. This is the biggest thing I miss when I open programs like Aseprite. I can't begin to describe how great it was for programming to be able to embed code inside of animation, and have the entire thing be a clip that could be embedded inside another program. Doing stuff like point-and-click games with that workflow was so fast and easy, and it was so easy to build up animations with a lot of disparate parts.
- a content-first workflow: related to the above, Flash let you switch between coding and content very quickly without worrying about stuff like imports. The fact that the content/animation and coding were so synchronized was a different way of thinking about architecture. There were problems associated with it when it came to scalability and organization, but again, just very fast to work with, very accessible, and lent itself to a certain way of thinking about prototypes that had some big advantages. When you had an idea you could be switching back and forth from code to animation constantly, you didn't have to alt-tab or export anything.
- AS2: maybe controversial, because AS3 was pretty popular and a lot of programmers were campaigning hard that it was the "correct" way to do things, but again, I want to stress the weird combination of content/animation/code was part of what made Flash special, and abstracting some of that out and having more "professional" content pipelines and different ways of doing events and organizing everything -- I think something was lost with that transition.
- Also just, in general, the animation tools were good. I don't know of an Open Source (or shared source) tool that has the same level of animation tools. Blender is doing some really compelling stuff that I'm very excited about, but Greasepencil is not a substitute for Flash, it's going in its own direction, and it's much less accessible. Aseprite is great (being able to tag frames and export data about them is handy), but it has some quirks and annoyances around the timeline controls. It's also just a lot more limited, you're basically forced to do frame-by-frame animation. There are some programs that I see animators online using that seem to be very powerful, but they're often either quite expensive or so restrictive and narrowly targeted that I'm not even willing to think about using them.
- And again, I can't stress enough: even just as an animation tool, even forgetting about games, adding scripting to animations is useful. You can have a movie clip that repeats until you hit a frame and throw an event. You can have a hand-animated scene with a procedurally animated background. And that's all really, really fast to do because the way the UX is set up you just have everything accessible at the same time.
----
I don't think it would be impossible to replicate some of the things that made Flash great, and if someone really took the time to sit down and think about what made that workflow what it was, I don't think it would be impossible to make a Flash replacement considerably better than Flash. Flash had bad audio tools, its data formats were all closed down, it wasn't really extensible, it's drawing tools could have been better, and for most of its life it was terrible if you wanted to do anything with non-vector content. There are big improvements that an Open replacement could make.
It would be an uphill battle, because the ecosystem surrounding Flash didn't just exist because of Flash. There are a bunch of different factors that went into it. And there are some APIs on the web that are still annoying. Mobile support for web games is still annoying. Controller support is not great, rumble isn't really supported. There's stuff we could do better. But the core functionality that old-school Flash needed is mostly there, and we could have (functionally) a Flash replacement today. It also wouldn't need to be a web app, you could have a Flash replacement that targeted the web for compilation that itself ran as a native app, and that would be completely fine.
Heck, you could have one that didn't target the web. Obviously I'm thinking first about the web, but if there was a Flash-equivalent Open Source prototyping tool that targeted Linux/Windows, that would also be great, and as far as I know that kind of tool also doesn't exist today.
It could be done, it would just be a lot of work to build, and tricky to get right and to get polished. The really weird reality is that as far as I can tell, no one's ever tried to build a Flash successor that actually imitated the features I care about in Flash. There are plenty of game dev platforms, some very easy to use, but very few of them have great content creation tools baked in, very few are experimenting with completely novel approaches to architecture like Flash's movie clip system.
This was just _magic_.
Godot and Unity prefabs are sort of half-way there, but the scene view being the primary interaction for editing causes the _magic_ to disappear. Flash had the timeline as the primary view; so where in scene view you drop an object into a space, in Flash you drop an animation into a timeline.
The outcome is very different. With time moving forward in the scene view, IE in Unity play mode, the objects in the world move and behave in a linear fashion. A ball rolls forward until it finds the lowest point to settle in. With time moving forward in the timeline the animations within loop endlessly. Time goes from 0 to N and back to 0 to repeat.
This was absolute _magic_ for rapid iteration.
And yes, all the rest you discussed was goodly, as well.
And it was an absolutely great cartoon animation toolkit.,
What is the status of that project, is it still active? What do you think of this project?
https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Sh...
It's entirely coincidental, but I love that I share the same name. For purely selfish ego reasons I wish it had succeeded.
That's not a dig at PICO-8, it's limited on purpose. But the strength of Flash was that it was extremely flexible and exposed an architectural style that lent itself very well to prototyping. PICO-8 does have all of its tools built into the same app, but it doesn't have anything at all like a movie clip system, it doesn't even have events or a timeline. I think it just has very different goals, it's a philosophy built around having a small, self-contained, understandable system -- not around having a unique workflow.
The closest programming/architecture analogy I draw to PICO-8 isn't Flash, it's the TI-83 graphing calculator. That platform also had a lot of influence over how I learned to program, and it had similar strengths to PICO-8 in how limited it was and how that forced you to get creative and allowed you to really deeply understand what was going on in your program.
Where I do see PICO-8 getting adjacent to Flash is in the community. I think when some people say they miss Flash, what they really miss is sites like Newgrounds and the surrounding indie scene. PICO-8 does capture some of that, it's a great environment to learn to code in, and it's a fun environment to work in. I just don't think it captures any of the tooling. When I say I miss Flash, I kind of miss the indie scene, but I miss the tooling more.
I'm honestly tempted to take a swing at the "open replacement" that you described in your original post..... Though I never actually used Flash back in the day, so I'd need to do some research
An interesting point here is that Adobe Animate still exists, which (in theory, I haven't used it) still has a lot of these features. But nobody uses it for game prototyping that I'm aware of -- and not just because it's expensive or (in my case) because people refuse to use subscription software. I've seen gamedevs do their animation in Animate CC, and then export it out to Unity. So there's something going on there.
I wonder if I went back and reinstalled Flash 8, if there are parts of it I would notice that didn't age well, or paradigms that needed to be rethought. But I still feel like that kind of workflow is something we could have again, and with enough thought put into it, it could be even better. I would welcome more people thinking about this kind of stuff or trying their hand at prototyping game engines that were designed around novel workflows.
There's fertile ground in this area if someone wanted to explore it and dig into it.
If you want to discuss this further, my email is in my bio!