assemblyscript VS goscript

This is probably the closest thing to that: https://www.assemblyscript.org/

We're going to write a fictional (and minimal!) firmware for our smart thermostat, let's assume we decided to use AssemblyScript (but it could have been in C, Rust, Go or any other supported language):

and have that just work without any JS "glue code". Maybe someday. I know they're working on the DOM APIs, but as you said, it's been slow going. Feels like priorities are elsewhere. Even CSS is moving forward with new features faster than WASM is (nesting and view transitions are awesome though).

(Btw when I said "separate runtime type checking" I didn't mean language-level; I was referring to the validation libraries that are required today since TS types obviously no longer exist after build. If it were a real static language, then of course you wouldn't need to do that because you can't store a bool in a string in the first place.)

[0]: https://www.assemblyscript.org/ (Porffor looks neat too. Wonder if it could be useful in plugin architectures? E.g. plugins can written in JS, and the program only needs a WASM interpreter. I'll bookmark it. Thanks.)

Built a platform flibbert.com where you can run code on ESP32 microcontrollers in AssemblyScript and TinyGo. It’s great for trying things out or learning without the usual setup hassle. Would love for people to try it and share feedback! (The project is on early stage, tested only on esp32-cam)

I get your point but one of the advantage of WASM is the compile step. It means that the WASM code will load and start running much faster because the browser gets a ready made binary to execute.

But yes, having the need for special tooling is a pain. My understanding is that AssemblyScript[0] allows to write code that look like Typescript and integrate well with the node ecosystem. Could be worth a look.

In case you start with a WAT file, there are ways to compile WAT to WASM in the browser[1].

[0] https://www.assemblyscript.org/

[1] https://webassembly.github.io/wabt/demo/wat2wasm/

I like your take but JavaScript was literally the assembly language of the web until WASM came along. There was no other language that TypeScript could compile to.

This train of thought lead me to discover AssemblyScript! https://www.assemblyscript.org/

Incidentally, it’s also what AssemblyScript uses: https://github.com/AssemblyScript/assemblyscript/blob/main/s...

Also see the more recently updated https://github.com/oxfeeefeee/goscript, “An alternative implementation of Golang specs, written in Rust for embedding or wrapping.”

Of course, another reason is to try to make Goscript useful :)

The README mentions it's already passing some cases, how much coverage do you have so far and how do you think it'll improve over time? Any sticky bits that you're worried about?

A cool project, a scripted Go implementation created from scratch and compiled to Wasm.

So I implemented a script version of Go in Rust, and with that I made a playground by compiling it to Wasm. It was so easy and worked just as I expected, and I got excited.

Someone already did that. https://github.com/oxfeeefeee/goscript

i've never used it but saw this this week, looked interesting: https://github.com/oxfeeefeee/goscript