Thomas Nattestad

@wesbos (Chrome's PM for the API here) If you have any feedback on the API don't hesitate to share it! github.com/WICG/html-in-c…

HTML in Canvas API is NUTS

@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 github.com/WebAssembly/sh…

@fractorious @ChromiumDev I’ve already tested SharedBuffer + multiple workers in Unity and in other applications with all the headers configured. But I always had the impression it was just a workaround, so I assumed that one day the browser companies would come up with an official solution

📢 WebGPU is now officially supported across Chrome, Edge, Firefox, and Safari → goo.gle/3MmN7Rj Access high-performance 3D graphics and AI capabilities right in the browser with this major milestone.

@microbians @ChromiumDev You should check out canvaskit skia.org/docs/user/modu… - 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!

@ChromiumDev Now we need a good 2D vector engine that jump into this + wasm could be cool

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

@fractorious @ChromiumDev First thing first. Could bad actors exploit WebGPU to train models, like Bitcoin minters do? Could it be exploited to mint crypto?

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

@ChromiumDev Why don’t we have a “WebNPU” API that gives direct, low-level access to the NPU the same way WebGPU gives to the GPU? Or #WebNN?

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

@ChromiumDev The only thing that’s missing is better multithreading!! Then I’ll be able to see AAA games running on them😝

@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: github.com/WICG/html-in-c… Share your creations!

For the last couple months, our team has been working hard on a few paradigm-changing features for HTML Canvas. One of them is the ability to have HTML elements in a canvas. Here's a ThreeJS demo with a live HTML texture.

@nullvoxpopuli Hey I'm the Chrome product lead for the V8 engine and JS language - want to schedule a call? nattestad@google.com

They propose this as a win-win. But I ultimately feel like some communication boundary has fallen apart, and we need to get better at communicating with implementers.

This presentation to TC39 has me *worried* for the future of JavaScript. I Do not like this phrasing. Let's dive in 👇 (1/35)

📣 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: 👇 kotl.in/kotlin-wasm-al…

@CraigThirtyFour @eastdakota @Cloudflare Wordpress in the browser has working PHP as a component :D web.dev/articles/wordp…

@eastdakota @Cloudflare Any chance PHP will ever get added?

That bet on #v8 as the underlying heart of @Cloudflare Workers looking pretty good right now. Or, put another way: support for Python, Java, Kotlin, and other garbage collected languages coming soon! v8.dev/blog/wasm-gc-p…

📢 Heads up, WebAssembly fans: we have a new Wasm collection! 👉 web.dev/wasm 👈 This is your one-stop shop for everything #WebAssembly (#Wasm) and #Emscripten, curated by WebAssembly DevRel @tomayac!

📢 Build in-browser WordPress experiences with WordPress Playground 🛝 and WebAssembly! developer.chrome.com/blog/wordpress… The full(!) WordPress powered by PHP running solely in the browser with WebAssembly 🤯. Learn how @adamzielin pulled this off! #WordPress #Wasm #WebAssembly #PHP

Just published our vision for how WebAssembly is changing how new web functionality can be delivered to developers! blog.chromium.org/2023/04/how-we…

@duckdb - I'm excited by your use of wasm in databases - we just released highly performant file access handles in Chrome ( web.dev/file-system-ac… ) 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!

@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!

🎉 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! web.dev/ps-on-the-web/

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

@RReverser Maybe that's something we can solve in WebCodecs? cc @fractorious

CSS pixels, <canvas> pixels and physical pixels on your screen are surprisingly independent — and that makes pixel-perfect rendering extremely hard. I wrote about a new ResizeObserver property that lets you measure the physical pixel size of an element! web.dev/device-pixel-c…

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

@gregwhitworth @marcosc Apple's view is also that we're willing to address these use cases if the security + privacy issues can be worked out. It's just that current specs + "just add a permission prompt" does not strike us as good enough. Browsing being safe is more important than HW access APIs.

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

@firt Should focus on PWA/NFC integration with a trusted way to link them (like TWAs have) and potentially allow the loaded app access to data from the NFC tag @fractorious

The Web loses again with AppClips. It had an opportunity with the Physical Web spec to create this ecosystem in an open and multiplatform way and it failed. Google is also responsible of that failure IMO.

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

@fractorious I understand that but you know how this works even if you standardize and you wish cross browser adoption. The web today includes iOS and iPadOS users and like it or not, the web today is not fugu. It's maybe what it can be, what we wish, what we expect but not what it is.

Is the web, the Chromium-based web? It's not just a semantic issue 🤔