trusktr

5 ms·

1.
by trusktr 4y ago
Two things: - speed up in some cases - ability to compile the same app to native
2.
by trusktr 4y ago
Node.js has reliable sandboxes for JS code without the need for Wasm.
3.
by trusktr 4y ago
Perhaps they are, but they don't want to.
4.
by trusktr 4y ago
Yes indeed, I got ASWebGLue (WebGL bindings for AssemblyScript) running in Node.js this way, with bindings to the webgl-raub package.
5.
by trusktr 4y ago
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 can with AssemblyScript. AS recently gained the ability
6.
by trusktr 4y ago
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?
7.
by trusktr 4y ago
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 Java or JavaScript yet).
8.
by trusktr 4y ago
> 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 year! :P I picked JavaScript thinking of AssemblyScript
9.
by trusktr 5y ago
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 will be eliminated. This seems like a better outcom
10.
by trusktr 5y ago
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. To remain compatible with TypeScript (which is AssemblyScri
11.
by trusktr 5y ago
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 about runtime interoperability between JS (with WTF-16 string
12.
by trusktr 5y ago
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 WebAssembly now: https://blog.scottlogic.com&#x2
13.
by trusktr 5y ago
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 is all about. They don't want to move to other language
14.
by trusktr 5y ago
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 data integrity issues that can lead to security issue
15.
by trusktr 5y ago
The poll will happen in this meeting on August 3rd: https://github.com/WebAssembly/meetings/blob/main/main/2021/...
16.
by trusktr 5y ago
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-inspired language) passing strings from one side to the oth
17.
by trusktr 5y ago
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 of engineering effort compared to having one form
18.
by trusktr 5y ago
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 irrelevant target compared to native. That's not what the w
19.
by trusktr 5y ago
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 a first-class feature with maximal performance and without
20.
by trusktr 5y ago
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 multiple string types? The idea is both AS and
21.
by trusktr 5y ago
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 concept isn't new. For example, fine-grained reactivity exist
22.
Writing a 3D scene with HTML(forums.infamous.io)
2 points by trusktr 10y ago|0 comments