#AssemblyScript
Spent the last days figuring out how to share community audio DSP code that can be run in both browser and native environments (securely). I have been looking into Faust, WASM, AudioWorklets, AssemblyScript, and others. The question is: What should users write DSP code in?
November 9, 2026 at 9:25 PM
Faust is cool, but not ideal for things like granular synthesis, because there is a fixed signal-flow graph. JavaScript is hard to translate to anything native. Rust is very powerful, but needs a compilation step for both browser (WASM) and native. With AssemblyScript, it's the same.
November 9, 2026 at 9:25 PM
`wasmrun ./project` compiles Rust, Go, C/C++, AssemblyScript or Python to WASM and serves it.

Web apps like Leptos get their own port and a control center beside them.
October 20, 2026 at 11:05 AM
Yeah which one? AssemblyScript to Wasm and wasm2c? Porffor? JS2? Static Hermes? Custom compiler with AI?
September 29, 2026 at 11:51 PM
We can skip Node.js, or Electron, and compile TS/JS to native. Soooooooo much easier to do these days with AIs. Several paths:

TS -> AssemblyScript -> Wasm -> wasm2c -> native

TS/JS -> Porffor -> native

TS/JS -> JS2 -> Wasm -> wasm2c -> native
September 29, 2026 at 5:25 PM
Yep, AssemblyScript will do that. There are some similar other AoT JS/TS-to-Wasm tools too.
September 24, 2026 at 5:31 PM
In about an hour, an AI agent was able to set up a pipeline to compile a stricter subset of TypeScript with AssemblyScript (all object shapes known up front) to native with wasm2c, statically linked to Chrome into a single binary. I was able to run a web app entirely as machine code without V8.
September 24, 2026 at 5:18 PM
I previously compiled TypeScript Custom Element code to WebAssembly. A next experiment will be to statically link to a browser directly. What's missing is my JS elements use decorators and template tag fns, which AssemblyScript does not support yet. That's a couple AI sessions away now though!
September 24, 2026 at 5:29 PM
I’ve been super excited for this to progress, though the excitement has been dampened somewhat by the concerns raised by the assemblyscript folks
September 20, 2026 at 5:11 PM
Example: in an hour I

- compiled TypeScript DOM code to native with AssemblyScript + wasm2c (I could replace those too!)
- statically linked directly to Chromium DOM APIs
- with the V8 JavaScript engine entirely bypassed
- with zero string copies so APIs like innerHTML read content from AS memory
Soon enough frameworks and libraries won't matter much. They'll all become just a documentation of preference or methodology.

We can pretty much one-shot prompt any framework these days, *and* have it taylored to our preferences.
September 15, 2026 at 10:05 PM
Pretty soon I'll compile my Lume 3D HTML custom elements to native.

I just need to vibe update (or replace) AssemblyScript to support decorators (my elements are written with decorators) to statically define reactive class fields.

I've already compiled non-decorated custom elements to Wasm.
September 15, 2026 at 10:05 PM
AssemblyScript maps very minimally to Wasm, so the runtime in the browser is very small compared to C/C++/Rust. Makes the bindings with JS very simple too. I've compiled Custom Elements to Wasm via AssemblyScript with my asdom bindings, so the next step would be adding a format.
February 19, 2026 at 12:03 AM
Yeah it basically comes down to agreeing on a data struct all languages can produce. I'd start with typed arrays from AssemblyScript which is TypeScript compilable to Wasm, and perhaps make libs for other languages to match the same structure. inevitably some libs are gonna be needed per language.
February 18, 2026 at 11:59 PM
How much faster is the C version than the Wasm version? Do you have a benchmark site? Any comparisons made with AssemblyScript.org (TS to Wasm compiler)?
AssemblyScript
A TypeScript-like language for WebAssembly
AssemblyScript.org
April 1, 2025 at 4:23 AM
AssemblyScript did something similar in a lot less time, with hobbyists.

Plus there's already a huge ecosystem of TypeScript code that exists, much if which could adjust to be compiled natively.

It wouldn't take that long like starting a brand new language from scratch.
March 13, 2025 at 10:41 PM
For reference here's the guide on writing portable code (code that can be compiled with both `tsc` or `asc`):

www.assemblyscript.org/compiler.htm...
Using the compiler | The AssemblyScript Book
How to use the compiler from the command line or as an API.
www.assemblyscript.org
March 13, 2025 at 7:02 PM
What I'm saying is if a couple of hobbyists at AssemblyScript already proved how, then a salaried team could do it a lot better, and it would still be cheap for Microsoft, while being a huge win for the TS/JS ecosystem.
March 13, 2025 at 7:01 PM
What are you guys talking about?

Have you seen AssemblyScript? Have you tried compiling TypeScript to JS with `tsc` and to Wasm with `asc`?

I've ported Three.js classes to TypeScript and gotten them compiled to both plain JS with `tsc` and Wasm with `asc`.
March 13, 2025 at 6:55 PM
TIL: binaryen.js
→ github.com/pdubroy/til...
May 25, 2025 at 2:04 PM
Thanks. Maybe it's not clear, my question is if there are other HLLs where I can write code that calls into to-be-generated-later Wasm. AssemblyScript makes this pretty easy; other languages (even "Wasm-first" ones like Moonbit) don't seem to, AFAICT?
May 23, 2025 at 6:12 AM
Are there any other languages that can do this?

This is AssemblyScript. I'm generating Wasm at runtime & linking some prebuilt AS code into the module. The call_indirect here lets me call from AssemblyScript into my generated code.

Not a super common use case, but so useful!
May 22, 2025 at 3:41 PM
We love typescript and assemblyscript
June 12, 2025 at 8:57 PM
Today's random GitHub ⭐!

christopher-kleine/wasm4-docker

Posted using Starrysky
GitHub - christopher-kleine/wasm4-docker
Dockerfile to create a docker image than compiles AssemblyScript, C, Go, Rust and Zig
github.com
June 23, 2026 at 4:31 PM