Thomas Nattestad

Product Manager of JavaScript, @v8js, #WebAssembly, and Advanced Capabilities (#Fugu project), WebGPU, and AI on the web.

[Thomas Nattestad @fractorious]

@wesbos (Chrome's PM for the API here) If you have any feedback on the API don't hesitate to share it! https://t.co/ozveaMnsSh

[Thomas Nattestad @fractorious]

@mepadev @ChromiumDev SharedArrayBuffer with workers running wasm modules is the official and standardized threading solution for linear memory languages like C++ & Rust. As it happens we are working on new threading primitives for GCed languages too https://t.co/rSnn58Rbmm

[Thomas Nattestad @fractorious]

@microbians @ChromiumDev You should check out canvaskit https://t.co/iULfmc53ga - it's the actual rendering engine of Chrome (Skia) compiled to wasm and enabled with WebGPU. Yes this does mean you're running Chrome's rendering engine on Chrome's rendering engine, but hey it works!

[Thomas Nattestad @fractorious]

@thakares @ChromiumDev A website could use WebGPU to do sandboxed GPU operations, which could (intentionally) include training a model. Chrome & other browsers do have some interventions in place such as when a site uses too much memory. I don't anticipate it'll be an issue for users.

[Thomas Nattestad @fractorious]

@thakares @ChromiumDev That is indeed what WebNN is for! Aiming for an Origin Trial in Q1. What is your use case?

[Thomas Nattestad @fractorious]

@mepadev @ChromiumDev Use WebAssembly multithreading! All this and more is possible on the web!

[Thomas Nattestad @fractorious]

@fserb Hi folks - this API is now live behind a flag and ready to test! We have the explainer here with instructions for trying out the API: https://t.co/y8mIIaLtZR

Share your creations!

[Thomas Nattestad @fractorious]

@nullvoxpopuli Hey I'm the Chrome product lead for the V8 engine and JS language - want to schedule a call? [email protected]

[Kotlin by JetBrains @kotlin]

📣 Kotlin/Wasm is now in Alpha and ready for you to try!

Build web applications with Kotlin and use Kotlin/Wasm in your KMP projects. Take it for a spin and share your feedback with us!

Learn more about the technology in this blog post: 👇
https://t.co/R5tOQq88ah

[Thomas Nattestad @fractorious]

@CraigThirtyFour @eastdakota @Cloudflare Wordpress in the browser has working PHP as a component :D https://t.co/x8fKslvN9l

[Chrome for Developers @ChromiumDev]

📢 Heads up, WebAssembly fans: we have a new Wasm collection!

👉 https://t.co/f8AQmSCjvH 👈

This is your one-stop shop for everything #WebAssembly (#Wasm) and #Emscripten, curated by WebAssembly DevRel @tomayac!

[Chrome for Developers @ChromiumDev]

📢 Build in-browser WordPress experiences with WordPress Playground 🛝 and WebAssembly!

https://t.co/8VORT4VstI

The full(!) WordPress powered by PHP running solely in the browser with WebAssembly 🤯. Learn how @adamzielin pulled this off!

#WordPress #Wasm #WebAssembly #PHP

[Thomas Nattestad @fractorious]

Just published our vision for how WebAssembly is changing how new web functionality can be delivered to developers! https://t.co/S0YkUwaur5

[Thomas Nattestad @fractorious]

@duckdb - I'm excited by your use of wasm in databases - we just released highly performant file access handles in Chrome ( https://t.co/xiONUMm3JY ) and a design goal for the API is for databases to build on top of it with wasm. Feel free to reach out if you want to chat!

[Thomas Nattestad @fractorious]

@ChromiumDev @adobemax It has been an absolute honor and pleasure to work on this for the last 3 years. Thank you to our amazing team and to Adobe for the amazing collaboration!

[Chrome for Developers @ChromiumDev]

🎉 Fantastic announcement from our partner Adobe at their annual @AdobeMax conference: Photoshop 🎨 is coming to the Web!

👉 Read up on how the Adobe and the Chrome team managed this incredible achievement and go check out the beta!

https://t.co/ePoFsMRc62

[Thomas Nattestad @fractorious]

@DasSurma @RReverser Do go checkout WebCodecs, I think that will give you raw access, even if not fully built just yet

[Thomas Nattestad @fractorious]

@othermaciej @marcosc @gregwhitworth So then why are permission prompts the answer for native apps?

Hardware access for web is less important *to Apple* because you have the native option, but not all web developers want to be iOS developers.

[Thomas Nattestad @fractorious]

@kennethrohde @firt I can't say I was a part of Chrome when we evaluated this, but I do remember looking at this once and deciding not to pursue. As you say, it wasn't technical (it never really is) but about what impact we could effectively have on the world. Gotta pick your battles.

[Thomas Nattestad @fractorious]

@firt I guess that means I have pretty good job security :D But more seriously, I do agree that we aren't there yet, but I genuinely believe we can get there over time.