proposals VS ruffle

Memory64 is supported by a lot of runtimes now, although it isn't fully standardized yet (see https://github.com/WebAssembly/proposals), so no idea how reliable the implementations actually are, since I haven't had a need for that much memory yet

Block only. There’s a tail call proposal[1] that’s in phase 4 (nearly standardized).

[1]: https://github.com/WebAssembly/proposals

While it'd be a nice addition, I wouldn't expect it any time soon.

It's currently still a stage 1 proposal, while we've been waiting for years for other proposals to be merged. The last time a proposal was actually finished was over 2 years ago.

https://github.com/WebAssembly/proposals

https://github.com/WebAssembly/proposals/blob/main/finished-...

Do you know anything about any WASM developments that will enable pure WASM interaction with browser's Web-APIs at no or at a low cost without the JS layer? I'm looking at https://github.com/WebAssembly/proposals and it's very confusing. There are type imports, almost complete GC proposal(which apparently only for GCd languages, but not for anything browser<->wasm), the component model(which looks and sounds as something not for the browser use case), JS String Builtins (which will provide faster JS strings, but not DOM) and ECMAScript module integration (which will turn WASM modules into ES modules, but Web-APIs aren't ES modules so no luck). Sometimes I read contributor interactions and it looks as if providing such functionality isn't their priority or even in their plans, and WASI + component model for cloud and similar use cases are more important.

It's already in Phase 4, so close: https://github.com/WebAssembly/proposals#phase-4---standardi...

Threads are Phase 3

https://github.com/WebAssembly/proposals

You can also check out:

https://webassembly.org/roadmap/

And for Go, the proposal project on Github has many interesting conversations from the devs.

And as a reminder to anyone interested in using Go WASM, it’s experimental and does not come with the same compatibility promise as Go itself:

https://github.com/golang/go/wiki/WebAssembly

GC proposal is from 2018: https://github.com/WebAssembly/proposals/issues/16 and there’s code: https://github.com/WebAssembly/gc/blob/master/proposals/gc/O...

Seems like an awefully long time for progress to be made, given all the possibilities it would unlock.

The proposal was recently bumped to stage 4 (the penultimate stage) with at least a couple of runtimes working on implementing (besides v8, which has supported it for quite awhile now)

https://github.com/WebAssembly/proposals

But basically it boils down to the memory control proposal, which can be found here and is not very far along; Webassembly proposals lists it in stage one.

FWIW, the thing I've found as the slowest single factor on my machine, might not be the slowest on yours; I might have not noticed the real cause of slowdowns on your machine at all, and you may be the only one able to diagnose it.

(and for the record, I'm on W10 too.)

Also, my personal experience from optimizing https://ruffle.rs/ is that in many cases Firefox's wasm runtime can behave slightly faster than on Chrome for some reason; and performance issues are often instead caused by other APIs like the canvas.

The proprietary tools were only an issue for people who needed the timeline. Games-wise, Both Actionscript 2 and 3 were perfectly usable without Flash. The MTASC compiler was a massive game-changer, and then Adobe released the AS3 compiler themselves, and certainly when I was at a consultancy working on a massive, expensive game, none of us were authoring anything in Flash. Even the designers and artists simply provided image assets.

A few years later, I did use Flash to teach students interactivity (in 2016, I was wondering why myself, but hey, university courses are hardly up-to-date) but there was little other reason to use it.

Today, I still rate AS3 and if there was an LLVM project to output, I don't know, WASM, or similar, I'd try it. Oh, there are?

- https://github.com/bvibber/wasm2swf

- https://ruffle.rs/

Of course, MTASC wunderkind Nicolas Cannasse went off to create https://haxe.org/, which was used quite well on Smart TVs and the like for a while, still used in games. Maybe we already have the answer, but the web is too boring for this stuff.

How about the same old flash emulated in wasm, so no plugin.

https://ruffle.rs/

Use those same great adobe tools in a vm.

If it used Flash, Ruffle would've picked them up (great addon if you haven't heard of it already: https://ruffle.rs/)

Looks like this site uses Windows Media Player embeds to play WMV files. I don't know of any big addon that makes those types of embeds work, if the server for the embedded protocol is still even alive.

Thankfully, the videos have been mirrored to Youtube.

Looks like this uses Flash (SWF) for interactive diagrams. Luckily ruffle.rs [1] works.

[1] https://ruffle.rs/

Some of you may know ruffle (https://ruffle.rs).

The memories…

I often wondered what would happen to those wonderful Orisinal mini games after Flash's death, without actually checking out the site. Would Ferry Halim find the time to port them to "HTML5"? Would they just… disappear forever?

It turns out that they know run in Ruffle[1], a Rust/WASM based Flash Player emulator I've never heard of (or forgotten about). The handful of them that I have tested work flawlessly.

[1] https://ruffle.rs/

shrug It finds its uses. It's just not that overstated.

sandspiel is quite popular and is built using WASM: https://sandspiel.club/

Google Earth - https://blog.chromium.org/2019/06/webassembly-brings-google-...

Ruffle (the "make Flash run safely" tool) - https://ruffle.rs/

Ableton's Learning Synths - https://learningsynths.ableton.com/

etc etc. It's just hard to tell when something is using WASM when it "just works" and is indistinguishable from optimized JavaScript

I was amazed that the site still runs, apparently still using the same engine.

But it seems that it was a flash site (of course), and archive.org seems to replace Flash Player with "Ruffle" [1]. Either that, or someone of Tobin's team replaced Flash with Ruffle >= 2019.

[1] https://ruffle.rs/