@frankel yeah, probably something like that! When I first heard about WASM I thought “thank god, I don’t have to use JS anymore”, but that assumption was also wrong and is now partly a non issue due to typescript. I wonder if there will be any “main stream” usage for WASM as it seems to be still a niche thing…
Someone big doing this has been such an inevitable development but it has taken so long! With #WASM now included in standards and supported in pretty much every browser there is an opportunity to treat the browser as the target platform abstraction for high performance stuff like #games. And there is nothing the actual underlying OS can do to gatekeep that content without breaking the web! https://www.gamedeveloper.com/mobile/microsoft-launching-web-based-mobile-game-storefront-in-july
@Migueldeicaza I was thinking this ever since you made .NET cross-platform way back in the day, but MS didn't manage to get it taken up as a standard in browsers.
I thought I would take up the challenge of getting @enhance_dev#WASM working with #aspnetcore with the ability to SSR web components directly into the request pipeline.
Without Nix, how do you set up complicated build/test environments on other systems? The sheer amount of sedimentary layers you need to do #WASM or #WebGPU stuff is astounding, and then you add the various utility Python libraries needed to glue together a test harness.
This gives a lot of people the possibility to begin using a platform with components that they already know and love -- and it gives the ability to target any arch or os with one "artifact". multiarch builds goes away here.
@squillace A key achievement of this spec is that a Wasm component in an OCI registry is conceptually still a component, rather than a wrapper that modifies the semantics of a component.
Among other things, this means that artifacts in OCI registries can continue to participate in component composition.
In this guide, aimed at web developers who want to benefit from #WebAssembly, you'll learn how to make use of #Wasm to outsource CPU-intensive tasks with the help of a running example.
GTK uses Vulkan by default on Wayland now. The migration from X to Wayland is super fascinating and intricate. I’ve been watching it unfold for years and have fought the urge to do deep dives. Future UI toolkits will continue to use multiple rendering engines and will facilitate compiling for desktop and/or browser which is going to reduce interest in JavaScript UI frameworks. There are frameworks that behave/look the same as desktop and Web applications.
@tomayac Uno Platform and egui are the two that come to mind. I know I’ve seen more but I can’t remember. If I do know send. I’m convinced there will be more moving forward.
@bsletten egui is on my list, too. I also have Qt Wasm and Avalonia UI. Then there's Flutter and Compose Multiplatform. Oh, and wxWidgets Wasm. I didn't have Uno Platform. Thanks for the reply!
Excited to listen to the first episode of @tomayac ‘s new WebAssembly podcast where he interviews Alon Zakai about the history and pre-history of #webassembly:
Hello World! Firefly Zero is an in-development handheld game console that runs #wasm and supports #BLE multiplayer. It is written by @orsinium in #Rust, runs on #ESP32, and will be fully open source (both software and hardware).
We already have a working desktop emulator and are getting a Rust and #golang SDK ready for alpha testing. Sounds fun? Stay tuned!
Learn about some early #WebAssembly history from one of the co-creators of #Wasm, Alon Zakai! Follow along how Alon explains how we came from Native Client to asm.js and then finally to WebAssembly, and explore some interesting historical and present day sidetracks on the way.
@teleclimber@kripken I guess it simply takes some time to propagate. It's also not yet to be found on Apple or Google Podcasts for example when I checked earlier.
Getting started with #WebAssembly? Let us point you in the right direction with videos on OS design, the component model, security features, generative AI and more! ▶️
This is the best job I've done conveying why I'm so enthusiastic about #wasm – or at least, the most succinct job I've done! We walk from the 1960's right up to the present day and, as a bonus, uh
@erlend that’s weird. I went back and checked the post and it does seem to have the correct link. I used Ivory to post, what client are you using to read it? Trying to find out if there is some sort of bug in Ivory’s autocomplete of usernames.
This talk by @esoterra introduces the idea of #Wasm "component-native" tooling, using Claw, a language built this way from the start.
It's obviously valuable to port existing language toolchains to Wasm. As we think about Wasm's future, it's also interesting to have component-native toolchains in the mix, because they have greater flexibility to take unconventional approaches, and find new creative ways of solving problems.
