interface-types
ruffle
interface-types | ruffle | |
---|---|---|
20 | 480 | |
636 | 14,517 | |
- | 1.2% | |
2.8 | 9.9 | |
about 2 years ago | 1 day ago | |
WebAssembly | Rust | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
interface-types
-
WebAssembly Playground
Some things that might greatly increase wasm usage and overall tooling:
1) Tools that run docker containers and serverless function services (like AWS lambda) to support providing a .wasm files instead
2) Garbage collection in the runtime to make GC languages easier to port to wasm
3) Dynamically typed languages (NodeJS, Python, Ruby) being able to compile to webassembly directly instead of porting the runtime to webassembly and then running the code through the runtime. This is a big ask though, basically needs to redesign the runtime completely
4) wasm-DOM bindings will enable other languages to do HTML rendering which will require new web frameworks for every language that wants to take over the space from JS. This will lead to (even more) fragmentation of the web ecosystem
5) A new wasm-first SDK (unrelated to the DOM) for building cross platform applications. I can see this taking off only if it is built-into the browsers and backed by some standards committee, so not very likely I think
6) Something like the Interface Types proposal ( https://github.com/WebAssembly/interface-types/blob/main/pro... ) becomes a thing allowing wasm programs to be consisted of modules written in several different languages and being able to call said modules with low or 0 runtime performance hit (and of course, no compilation to multiple CPU archs). So much of programming ecosystems are locked to specific languages (like data science with python) when there is little technical reason for it be like that.
-
Bring garbage collected programming languages efficiently to WebAssembly
AFAIK GC is irrelevant for "direct DOM access", you would rather want to hop into the following rabbit hole:
- reference types: https://github.com/WebAssembly/reference-types/blob/master/p...
- interface types (inactive): https://github.com/WebAssembly/interface-types/blob/main/pro...
- component model: https://github.com/WebAssembly/component-model
If this looks like a mess, that's because it is. Compared to that, the current solution to go through a Javascript shim doesn't look too bad IMHO.
-
Rust & Wasm (Safe and fast web development)
I'm not really optimistic that particular aspect will get much improvement. Many people expected interface types to come save the day, but after a looong stagnation that proposal has been archived (for now) in favour of component types, which has much less potential for performance gains.
-
Plugins in Rust: Wrapping Up
Really good questions. Unfortunately, most of the issues I found back then were fundamental ones. I've seen that Wasm has deprecated "Interface Types" and is now working on the "Component Model". But even then, as far as I understand that would only avoid the serialization and deserialization steps, and you would still need to copy complex types. It will be more performant, but I don't think it would be enough for Tremor either.
-
When moving from JS to WASM is not worth it - Zaplib post mortem
wasm doesn't know anything about the outside world on purpose. This allows it to be used in other domains. For direct access to the DOM et al, interface types are being developed. It's a non-trivial problem to interoperate with a dynamically typed GC'd language from any statically typed no-GC language that can compile to wasm.
-
WebAssembly 2.0 Working Draft
You may want to look into WASM interface types, which is defining what amounts to am IDL for WASM and different languages have common calling conventions: https://hacks.mozilla.org/2019/08/webassembly-interface-type...
I don’t know if there’s a better intro article. I believe this is the current iteration of the proposal: https://github.com/WebAssembly/interface-types/blob/main/pro...
-
Replace JS with Rust on front-end, possible? Advisable?
Yes, and if I'm not mistaken, this is the RFC
-
Google Chrome emergency update fixes zero-day used in attacks
I see no reason why not. See the interface types proposal for a proposed solution.
- Rust for UI development
-
Front-end Rust framework performance prognosis
Wanted to get thoughts from the Rust experts on this - the author of the Yew framework seems to think that Web Assembly Interface Types (https://github.com/WebAssembly/interface-types/blob/master/proposals/interface-types/Explainer.md) will allow Yew to eventually become faster than Vue, React, Angular, etc. Is there general consensus on this in the Rust community? The prospect of mixing Rust (for the performance critical pieces) with TS on the front end doesn't seem super appealing to me.
ruffle
-
Orisinal: Morning Sunshine (recovered old flash games)
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/
-
WebAssembly Playground
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
-
Amon Tobin – Foley Room site (2007)
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/
-
New York Times Flash-based visualizations work again
Out of curiosity a couple months ago I wondered if I could play my old Proximity flash game on Newgrounds from the browser within the Quest 3 VR headset, and it worked great!
That led me to do a little searching, and I discovered that originally the game didn't work in Ruffle, as I apparently did something with the play game button that wasn't normal. But someone put a fix in it back in 2020[1] in order to get my game working again. That was pretty neat. Felt kind of nice that people still cared enough about my old game to make sure it still works in an emulator.
Still working on a more in-depth sequel (using Monogame), and I'm way overdue to make a new web version of the original. Might knock that out once I get closer to getting the sequel out there.
[1]: https://github.com/ruffle-rs/ruffle/pull/1024
-
New York Times has added a web-based Flash player to their archive website
i believe it's using Ruffle[0] and that's already happened[1]
[0] https://github.com/ruffle-rs/ruffle
-
It's the offseason, so it's time to face the most lethal bullpen ever assembled. Let's play Winnie the Pooh's Home Run Derby!
This is all using a really cool Flash emulator called https://github.com/ruffle-rs/ruffle
- you can still play flash games without using adobe flash player thanks to ruffle
- Você lembra dos jogos em Flash?
- A Flash Player emulator written in Rust
- Ruffle: Flash Player Emulator
What are some alternatives?
assemblyscript - A TypeScript-like language for WebAssembly.
lightspark - An open source flash player implementation
gc - Branch of the spec repo scoped to discussion of GC integration in WebAssembly
Offline-flash-player
ASP.NET Core - ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
react-resizable-and-movable - 🖱 A resizable and draggable component for React.
Blazor.WebRTC
TIC-80 - TIC-80 is a fantasy computer for making, playing and sharing tiny games.
meetings - WebAssembly meetings (VC or in-person), agendas, and notes
launcher - Launcher for Flashpoint Archive
proposals - Tracking WebAssembly proposals
jpexs-decompiler - JPEXS Free Flash Decompiler