this post was submitted on 10 Sep 2023
77 points (100.0% liked)

Programming

13376 readers
1 users here now

All things programming and coding related. Subcommunity of Technology.


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] RandoCalrandian@kbin.social 72 points 1 year ago (14 children)

Refusing rust and wasm is a signal you don’t care about code quality or security

See? You can keep playing that game all the way down to the most onerous language

[–] SketchySeaBeast@lemmy.ca 3 points 1 year ago (2 children)

Can wasm manipulate the DOM yet?

[–] TehPers@beehaw.org 3 points 1 year ago

It can with some glue code that you better be writing in TypeScript if you care about code quality.

(As far as I know, it can't manipulate the DOM directly. Maybe things changed in the past couple months since I checked, but I doubt it.)

[–] abhibeckert@beehaw.org 1 points 1 year ago* (last edited 1 year ago)

WASM allows arbitrary code execution in an environment that doesn't include the DOM... however it can communicate with the page where the DOM is available, and it's trivial to setup an abstraction layer that gives you the full suite of DOM manipulation tools in your WASM space. Libraries for WASM development generally provide that for you.

For example here's SwiftWASM:

let document = JSObject.global.document

var divElement = document.createElement("div")
divElement.innerText = "Hello, world"
_ = document.body.appendChild(divElement)

It's pretty much exactly the same as JavaScript, except you nee to use JSObject to access the document class (Swift can do globals, but they are generally avoided) and swift also presents a compiler warning if you execute a function (like appendChild) without doing anything with the result. Assigning it to a dummy "underscore" variable is the operator in Swift to tell the compiler you don't want the output.

load more comments (11 replies)