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.
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:
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.
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! ▶️
> I mean, you get problems if you try to launch a thread…
Which specific problems are you refering to?
As far as I understand, you can spawn threads in JS environments (e.g. in the browser) with no problems (using Web Workers and SharedArrayBuffer under the hood).
Only spawning them in non-JS environments is currently not supported, if I'm not mistaken. For this, we'll need the thread-spawn proposal implemented, right!?
Just updated all https://thi.ng/wasm-api packages, bindgen, build scripts, readmes and examples to be compatible with the brand new Zig v0.12.0 released a couple of days ago... This includes adapting to breaking changes (esp. Zig's build system) and updating the hybrid Zig/WASM/TypeScript project template:
@enhance_dev Backend agnostic server-side rendering (SSR) for Web Components
> https://enhance.dev is an HTML-first full-stack web framework that gives you everything you need to build standards-based multi-page web apps that perform and scale. #Enhance apps and their elements are server-side rendered for incredible performance and seamless progressive enhancement.
This is huge. I’ve been bullish on RISC-V from the beginning but this is happening even faster than I expected. Between IT Sovereignty and geopolitics involving access to global supply chains, hyperspecialization of algorithms to hw, etc., it’s about to get really interesting.*
We’re one generation from the tech hacking culture of cyberpunk fiction.
HW heterogeneity will be mediated by LLVM and WebAssembly.
Drumming up some excitement 🥁… I just recorded the first episode of a new podcast series that I'm hosting: the #WasmAssembly, your monthly podcast gathering of people to geek out about all things #WebAssembly.
My first guest was no other than #Wasm OG @kripken, whom you may associate with projects like #Emscripten and, you know, WebAssembly, the language. The episode should go up mid April, watch this space!
Yes. It's WasmAssembly, a name smarter than hairdresser 💇 names à la United Hairlines.
I mean, if we am able to run NEXTStep on my browser, what stops me from running all retro games in the browser, without the need of emulators or complex setups?
WASI 0.2 is here ✨ the Component Model unlocks #webassembly's potential outside the browser, and brings with it a fundamentally different way to build for the #web and beyond.
#Wasm components are language-agnostic units of code, that use more secure interaction and communication methods, and unlock exciting potential for the future of composability and compatibility.
In the talk, we showed a lot of examples of how Google uses #Wasm in its products, creates tooling for Wasm, and contributes to Wasm's standardization.
For questions, catch either of us at the #wasmIO conference.