Viewing profile — trusktr

Two things: - speed up in some cases - ability to compile the same app to native

Node.js has reliable sandboxes for JS code without the need for Wasm.

Perhaps they are, but they don't want to.

Yes indeed, I got ASWebGLue (WebGL bindings for AssemblyScript) running in Node.js this way, with bindings to the webgl-raub package.

That's definitely interesting, but seems a bit less convenient compared to, for example, writing some TypeScript (compiled to Wasm) and importing that into the JS like we already c…

I was thinking to fork a browser engine, and bind wasm directly to the DOM without any JS. Anyone interested in teaming up on this?

You can do that with bindings currently. Interface types should only make it easier (for languages with utf-8 strings, as interface types does not support WTF-16 strings like in Ja…

> I do wonder whether some respondents are incorrectly identifying AssemblyScript as JavaScript? Perhaps we should include HTML and CSS in the list of languages to choose from next…

If Interface Types doesn't convert WTF strings to UTF, the flaw won't have to be documented, and the risk that someone forgets to do the right thing and causes a program to break w…

AssemblyScript is a compiler that aims to compile TypeScript code (with slight differences to be able to make sense in Wasm, though trying to minimize those differences) into Wasm.…

This is exactly right. UTF-8 is the transmission format that your HTML gets sent in, but it is not the format of strings in JavaScript at runtime. The problem being discussed is ab…

I think you're mistaken there: AssemblyScript is much newer, it's momentum is only just getting started. AssemblyScript is one of the top three most desired languages for WebAssemb…

It is fair to like Rust, but there is nonetheless an influx of web developers who already know JavaScript and TypeScript moving to AssemblyScript to (finally) experience what Wasm …

Yep, it will impact any language with WTF-16. Those languages may incur a performance hit if the vote passes to not support "expressive UTF-16", but more notably, there will be dat…

The poll will happen in this meeting on August 3rd: https://github.com/WebAssembly/meetings/blob/main/main/2021/...

The upcoming Interface Types spec for WebAssembly was thinking to not support WTF-16 string format, which means any Wasm modules (for example those written in AssemblyScript, a web…

How would an end developer write code in one fashion (f.e. `let foo: string = "hello "`) while the compiler makes that work perfectly in every scenario? It would take a high amount…

Because if they did, then interop with JS would require performance-losing conversion any time a string needs to be sent from one side to the other, making Web a secondary and irre…

Yes, but WebAssembly operates at the boundary with JS, and that is not UTF-8. JS uses WTF-16 at runtime, and if WebAssembly did too then this would make interop between Wasm and JS…

Note that AssemblyScript rides on TypeScript language syntax. How would ``` let foo: string = "whatever" ``` be able to work in any similar sense as TS/JS if? How can that map to m…

Solid took what in theory everyone knew would be the best approach to UI tree manipulation and composition, and made the theory come true: reactive fine-grained updates. The concep…