Refusing TypeScript is a signal that you don't care about code quality

vitonsky@programming.dev to Programming@beehaw.org – 77 points –
Refusing TypeScript is a signal that you don't care about code quality
vitonsky.net
65

You are viewing a single comment

Can wasm manipulate the DOM yet?

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.)

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.