It wouldn't be too difficult to make something even better than flash that emitted wasm files, that could run everywhere. It would give lots of folks a creative outlet that could be infinitely shared.
Yes. The authoring tool was the brilliance of flash. It allowed non-coders to make interactive things really easily.
Anyone whose made an Instagram filter or TikTik effect recently - it was like that, though even easier, but allowing you to do actual coding right down to very low level stuff should you desire.
and you could get push your creation to any screen in the known universe with essentially zero testing.
That program shaped my brain in ways I can't articulate. Took things I learned about computers and animation as an 11yo for granted as basic knowledge.
The flash runtime was pretty efficient but the authoring tools were so easy to use that anyone could produce "working" abominations filled with the most good awful code that got the result they wanted.
Having never used the authoring tool, can you point me towards something to model it after?
I think a Bret Victor, "Inventing on Principal" style editor would be perfect, combined with some sort of scratch like Python IDE where each element is defined in terms of its reactive behaviors with other elements on a timeline.
I didn't say easy, I said not too difficult. Order of magnitude difference. :)
IMO, it’s not the technology that matters but the authoring tools. Flash was easy to pirate, sometimes free with school, and easy to use. Thinking of applications as “animations with scripting” was a great idea because it let people only learn what they wanted to.
If you just want to make animations, skip actionscript entirely. If you want some extra Easter eggs, just turn any symbol into a button and you can trigger any movie clip you want. Want to make this a whole game, heres the whole action script editor.
I don't think so, Flash Player was extremely stable and portable, swfs ran accurately (although sometimes slowly) on all targets, Safari, IE7, Nintendo Wii, didn't matter.
Maybe wasm+Canvas is getting close to being stable. But if you code up a webgl game and test it on desktop Chrome, odds are it'll just be a black screen on anything but the most popular Android devices, and you'll need to do tons of work and testing to get it to run on an iPhone.
And WebGPU is probably at least 5 years away from being stable enough to be considered to "run everywhere".
I strongly considered trying to do this a few times, but ended up writing an swf parser in C++ and used Skia to render. It's probably the best we can do right now, but we still regularly get players who complain about just seeing a black screen.
Godot is too complicated compared to Flash. Have you ever used Flash? In Flash, you could literally take the brush from the toolbox, draw a circle, and that was your player character. That was it. No importing assets, no creating sprites, no nothing. You literally draw the circle right there with vector art tools, and it can be whatever you want.
And those were THE best vector art tools, because when you drew a shape and the shape overlapped with another, it automatically erased the other shape like you would expect it to in a raster graphics editor. In pretty much every other software I tried, e.g. Inkscape, Affinity, Corel Draw, Illustrator, you just get two separate shape objects one on top of the other. They seem to be designed for drawing the outlines, not to actually paint with brushes. Flash understood what was intuitive for artists.
Honestly, the older I get the stranger I feel about the fact that there was a brilliance in creating interface for people to be productive with back then that seems to be completely gone. I think this may be in part because desktop applications are unusual nowadays, but it's just really strange that the things I remember seeing have been done exactly once and never copied by anybody despite how well they worked.
It doesn't in high-school visual basic seemed to have had a 50% pickup rate based on final project quality (closest I can think of to Godot that I actually saw) , Flash nearly everyone/group had a viable thing to show off for the final project.
Building a good tool is the problem. For instance Git was born in a very niche community (kernel programming), yet it spread like wildfire. Despite the shortcomings of its CLI (according to some), and despite the fact there was other well'established tools.
As someone that would rather use Mercurial and was perfectly fine with Subversion, that wild fire was "Linux kernel uses it, was made by Linus, and I want to be cool like Linus".
Rather than a weird "cult of personality", the fact that Git demonstrated with Linux that it could handle a relatively large amount of source code and allow dozens (hundred?) of programmer to work on it "asynchronously" were key factors for adoption, I believe. If SVN was that good, as it was already well-established online (Github was not the first online VCS frontend, far from it), it should have remained the king of the hill. But it was decapitated instead.
I am been using FOSS and commercial source management tooling since 1998, and the very fact that Linus only bothered with git due to BitKeeper changing their licence, proves that there was nothing special about it, other than personality and adoption wave.
Game development often uses commercial solutions like perforce that have central servers so you can lock out your binary files and everyone will know not to touch them at the same time as you.
I think I’ve seen SVN in a single studio in the past decade. It’s almost all Perforce, because of better performance and tooling and the Unreal integration.
And yes, locking unmergeable files is essential either way.
A side effect of the great idea to write application software in Python that perdures to this day, still it was fast enough for purpose, it isn't like doing SCM operations is akin to 120 FPS for a game engine.
It isn't great that are now so many Git GUI clients written in Electron?
The problem with Python CLI tools is startup time. Just firing up the interpreter and importing modules can take a frustratingly long time if you're a twitchy CLI user. That's much less of a problem for a GUI tool that tends to sit open for a while.
