shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

269
active users

#wasm

1 post1 participant0 posts today
openSUSE Linux<p>Curious about <a href="https://fosstodon.org/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAssembly</span></a> but don’t know where to start? Follow the fun journey explained at <a href="https://fosstodon.org/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openSUSE</span></a> Conference of porting Little Piggy Tracker (a Game Boy-inspired audio app) to handhelds &amp; the browser. <a href="https://fosstodon.org/tags/oSC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>oSC25</span></a> <a href="https://fosstodon.org/tags/WASM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WASM</span></a> <a href="https://youtu.be/pq-04MlLAnM?si=m4y_MdO-dkh7wV11" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtu.be/pq-04MlLAnM?si=m4y_Md</span><span class="invisible">O-dkh7wV11</span></a></p>
Make Kasprzak 🦖🍁<p>PLAYING GAMES ON BLUESKY?? 🕹️😱 Not just on Bluesky, but IN @bsky app! 🤯 Please LIKE and SHARE this if you'd like this as a feature! <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23atdev" target="_blank">#atdev</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23atproto" target="_blank">#atproto</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23chaos" target="_blank">#chaos</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23gamedev" target="_blank">#gamedev</a> <a class="hashtag" rel="nofollow noopener" href="https://bsky.app/search?q=%23wasm" target="_blank">#wasm</a><span class="quote-inline"><br><br>RE: <a href="https://bsky.app/profile/did:plc:svpym4ujks7qxczscyzq7fuy/post/3lstioe7p622b" rel="nofollow noopener" target="_blank">https://bsky.app/profile/did:plc:svpym4ujks7qxczscyzq7fuy/post/3lstioe7p622b</a></span></p>
vruz<p>Direct WASM→DOM access doesn't leave JavaScript behind - JS could use the same fast path! We could even build Fagnani's exact templating API as a reference implementation on top of it. But unlike a JS-only solution, the platform stays open for potentially superior approaches in ANY language. Rust might build something faster. Zig might build something smaller. That's the kind of competition through collaboration that drives innovation. Everybody wins wins wins. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>javascript</span></a></p>
vruz<p>Instead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frontend</span></a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a></p>
vruz<p>The performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>performance</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a></p>
vruz<p>Instead of standardizing one templating syntax (that'll be bikeshedded to death), give us the primitive: fast DOM access from any language. Let a thousand templating libraries bloom - in any language. Lower-level primitives enable more innovation than high-level APIs. That's the Unix philosophy. Simple, composable, powerful. Build the foundation right. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frontend</span></a> <a href="https://mstdn.social/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a></p>
vruz<p>The performance argument for native templating is weak - we're talking 2% gains, max. But remove the JS bridge for WASM? That's where real performance wins live. Fix the actual bottleneck. Every DOM call through JS is overhead we don't need. Direct access would unlock true native speeds for web UIs. Imagine game engines manipulating DOM at 60fps without JS overhead. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/performance" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>performance</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a></p>
vruz<p>Why add yet another JS templating API when WASM + direct DOM access solves the root problem? Every language could build efficient UIs without the JS bottleneck. More universal than blessing one syntax. Think beyond JavaScript - imagine Rust components with zero overhead, Go templates that actually perform, or C# Blazor without the bridge tax. That's true platform evolution. <a href="https://mstdn.social/tags/compsci" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>compsci</span></a> <a href="https://mstdn.social/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webdev</span></a> <a href="https://mstdn.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mstdn.social/tags/webstandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webstandards</span></a></p>
Karsten Schmidt<p>Various thi.ng updates, bug fixes, additions and new version of <a href="https://github.com/thi-ng/zig-thing/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/thi-ng/zig-thing/</span><span class="invisible"></span></a> — now fully compatible with current Zig v0.14.1</p><p>On a more diary/devlog note: I also updated several of my Zig based work-in-progress art pieces to the latest version (some of them not touched in 2+ years) and it's so good to see how the <a href="https://thi.ng/wasm-api" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/wasm-api</span><span class="invisible"></span></a> toolchain has been holding up with various breaking Zig changes and also how this setup simplifies creating hybrid Zig/TypeScript projects (e.g. for using DOM/WebGL from Zig). Related, I also want to mention once more the <a href="https://mastodon.thi.ng/tags/GenArtAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenArtAPI</span></a> Zig WebAssembly bindings[1] (updated a few weeks ago), which add another layer of flexibility &amp; boilerplate reduction for generative/procedural/algorithmic art projects...</p><p>I will be attempting yet another few takes creating a video overview &amp; mini-workshop/tutorial about <a href="https://thi.ng/genart-api" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/genart-api</span><span class="invisible"></span></a>, hopefully also touching on these aspects...</p><p>[1] <a href="https://github.com/thi-ng/genart-api/tree/main/packages/wasm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/thi-ng/genart-api/t</span><span class="invisible">ree/main/packages/wasm</span></a></p><p><a href="https://mastodon.thi.ng/tags/ThingUmbrella" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ThingUmbrella</span></a> <a href="https://mastodon.thi.ng/tags/Zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Zig</span></a> <a href="https://mastodon.thi.ng/tags/Ziglang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ziglang</span></a> <a href="https://mastodon.thi.ng/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAssembly</span></a> <a href="https://mastodon.thi.ng/tags/WASM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WASM</span></a> <a href="https://mastodon.thi.ng/tags/GenArtAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenArtAPI</span></a> <a href="https://mastodon.thi.ng/tags/Art" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Art</span></a> <a href="https://mastodon.thi.ng/tags/GenerativeArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeArt</span></a> <a href="https://mastodon.thi.ng/tags/AlgorithmicArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AlgorithmicArt</span></a></p>
just small circles 🕊<p>Hi <span class="h-card" translate="no"><a href="https://mastodon.neilzone.co.uk/@neil" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>neil</span></a></span> the gist of this may be interesting (without the AI, and the project isn't open source afaics):</p><p>&gt; I [built] Tritium. Tritium aims to be the <a href="https://social.coop/tags/lawyer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>lawyer</span></a>'s <a href="https://social.coop/tags/VSCode" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VSCode</span></a>: an all-in-one drafting cockpit that treats a deal's entire document suite as a single, searchable, AI-enhanced workspace while remaining fast, local, and secure.</p><p>&gt; Tritium is implemented in Rust. It is cross-platform and I'm excited for the prospect of lawyers running <a href="https://social.coop/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> as their daily driver.</p><p><a href="https://news.ycombinator.com/item?id=44256765" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">4256765</span></a></p><p><a href="https://social.coop/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a></p>
Karsten Schmidt<p><a href="https://mastodon.thi.ng/tags/ReleaseMonday" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReleaseMonday</span></a> — New version (v0.27.0) of <a href="https://thi.ng/genart-api" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/genart-api</span><span class="invisible"></span></a>, a platform-independent extensible API for browser-based computational/algorithmic/generative art projects:</p><p>This version features an overhaul of the platform provided PRNG (pseudo-random number generator) handling and makes it easier to create multiple PRNGs for artworks which require/desire them...</p><p>Related section in the README:<br><a href="https://github.com/thi-ng/genart-api/blob/main/README.md#determinism--prng-provision" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/thi-ng/genart-api/b</span><span class="invisible">lob/main/README.md#determinism--prng-provision</span></a></p><p>Also, just as a reminder, the project has:</p><p>- no external dependencies<br>- adapters for 3 art platforms (EditArt, fxhash, Layer)<br>- 6 example projects<br>- testing/dev sandbox with two parameter editors<br>- WebAssembly bindings &amp; demo (currently for <a href="https://mastodon.thi.ng/tags/Zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Zig</span></a> only)</p><p>Happy coding! :)</p><p><a href="https://mastodon.thi.ng/tags/GenArtAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenArtAPI</span></a> <a href="https://mastodon.thi.ng/tags/GenerativeArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GenerativeArt</span></a> <a href="https://mastodon.thi.ng/tags/AlgorithmicArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AlgorithmicArt</span></a> <a href="https://mastodon.thi.ng/tags/ProceduralArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ProceduralArt</span></a> <a href="https://mastodon.thi.ng/tags/Art" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Art</span></a> <a href="https://mastodon.thi.ng/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a> <a href="https://mastodon.thi.ng/tags/Parameters" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Parameters</span></a> <a href="https://mastodon.thi.ng/tags/Interoperability" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Interoperability</span></a> <a href="https://mastodon.thi.ng/tags/TypeScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TypeScript</span></a> <a href="https://mastodon.thi.ng/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JavaScript</span></a> <a href="https://mastodon.thi.ng/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAssembly</span></a> <a href="https://mastodon.thi.ng/tags/WASM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WASM</span></a> <a href="https://mastodon.thi.ng/tags/Ziglang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ziglang</span></a></p>
Oto Šťáva<p>Had to move half of the game view code around for this, but totally worth it! (And I would be moving it at some point anyway) </p><p><a href="https://mastodon.social/tags/gamedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gamedev</span></a> <a href="https://mastodon.social/tags/zig" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zig</span></a> <a href="https://mastodon.social/tags/ziglang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ziglang</span></a> <a href="https://mastodon.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://mastodon.social/tags/webassembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webassembly</span></a></p>
Linus Gasser<p><span class="h-card" translate="no"><a href="https://infosec.exchange/@gabe_sky" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gabe_sky</span></a></span> That's a great page - it's always the first 10 links on Google you need to skip usually :)</p><p>I took the time to work on my DHT-based storage system running in the browser, and now it works nicely with simple javascript:</p><p><a href="https://danu.li/#web/qrcode" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">danu.li/#web/qrcode</span><span class="invisible"></span></a></p><p>If you connect through the above link, your browser becomes a node in a decentralized network, and fetches this page from one of the other nodes! For more information, visit</p><p><a href="https://danu.li" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">danu.li</span><span class="invisible"></span></a></p><p><a href="https://social.epfl.ch/tags/DHT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DHT</span></a> <a href="https://social.epfl.ch/tags/web3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>web3</span></a> <a href="https://social.epfl.ch/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> <a href="https://social.epfl.ch/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a></p>
Anirudha<p>🌀 Introducing **Chakra** - a blazing fast in-browser WebAssembly runtime for builders.</p><p>```sh<br>chakra myfile.wasm<br>```</p><p>– Runs WASM in-browser with logs<br>– Supports Rust, TinyGo, C, Asc and Python<br>– One-line introspection &amp; verify commands</p><p>Chakra is an open source project and we're building it *with the community*. </p><p>🌟 <a href="https://github.com/anistark/chakra" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/anistark/chakra</span><span class="invisible"></span></a><br>📖 Read more: <a href="https://blog.anirudha.dev/chakra" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">blog.anirudha.dev/chakra</span><span class="invisible"></span></a></p><p>Give us a shout-out or star the repo on github if you like the idea. 🙌</p><p><a href="https://fosstodon.org/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://fosstodon.org/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://fosstodon.org/tags/devtools" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>devtools</span></a> <a href="https://fosstodon.org/tags/rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rust</span></a> <a href="https://fosstodon.org/tags/webassembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webassembly</span></a></p>
Brian Swetland<p>Ruffle remains the most compelling argument for Rust and WASM as technologies. Anything that allows one to once again experience sbemails in their original vector-art glory is clearly a net positive for society.<br><a href="https://homestarrunner.com/sbemails/58-dragon" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">homestarrunner.com/sbemails/58</span><span class="invisible">-dragon</span></a></p><p><a href="https://chaos.social/tags/Rust" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rust</span></a> <a href="https://chaos.social/tags/WASM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WASM</span></a> <a href="https://chaos.social/tags/sbemail" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sbemail</span></a> <a href="https://chaos.social/tags/Trogdor" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Trogdor</span></a> <a href="https://chaos.social/tags/StrongBad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>StrongBad</span></a></p>
jbz<p>⚡ Why I use WebAssembly | nasso.dev</p><p>「 My favorite way to use WebAssembly is as a way to share code between platforms. Write the core logic of your application in Ru… a language that can easily compile to native code and WebAssembly 😊. In this architecture, most of your code is shared between the “native” and the “web” variants of your app 」</p><p><a href="https://nasso.dev/blog/why-i-use-wasm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">nasso.dev/blog/why-i-use-wasm</span><span class="invisible"></span></a></p><p><a href="https://indieweb.social/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://indieweb.social/tags/webassembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>webassembly</span></a></p>
Tanguy ⧓ Herrmann<p>Have you seen this absolute crazy demo?</p><p><a href="https://www.youtube.com/watch?v=kGBeT8lwbo0" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=kGBeT8lwbo</span><span class="invisible">0</span></a></p><p>plan9-like OS, accessed via a shell, from a wasm binary that allows to change the webpage DOM dynamically with the VFS and run processes in the background as well.</p><p><a href="https://hachyderm.io/tags/golang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>golang</span></a> <a href="https://hachyderm.io/tags/plan9" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>plan9</span></a> <a href="https://hachyderm.io/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://hachyderm.io/tags/wasi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasi</span></a> <a href="https://hachyderm.io/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unix</span></a> <a href="https://hachyderm.io/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p>
Karsten Schmidt<p>This is may really be just news to me, but today I learned that <span class="h-card" translate="no"><a href="https://hachyderm.io/@dubroy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>dubroy</span></a></span>'s and <span class="h-card" translate="no"><a href="https://hachyderm.io/@marianoguerra" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>marianoguerra</span></a></span>'s book "WebAssembly from the Ground Up" has actually been available for a while and the topics look super interesting...</p><p><a href="https://wasmgroundup.com/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">wasmgroundup.com/</span><span class="invisible"></span></a></p><p>Top level topics (quoting from their website):</p><p>- What exactly WebAssembly is, and what makes it unique.<br>- How to instantiate a WebAssembly module in JavaScript and run its functions.<br>- The binary module format, and how to hand craft a module from scratch.<br>- How to create a simple compiler with Ohm.<br>- The instruction set: numeric instructions, memory access, control flow, etc.<br>- How to interact with the outside world.<br>- The WebAssembly security model: what makes it safe?</p><p>(Ps. If you're looking to combine this new knowledge and are interested in building hybrid JS/TS/WASM apps, also check out my extensible <a href="https://thi.ng/wasm-api" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="">thi.ng/wasm-api</span><span class="invisible"></span></a> toolchain...)</p><p><a href="https://mastodon.thi.ng/tags/Book" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Book</span></a> <a href="https://mastodon.thi.ng/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAssembly</span></a> <a href="https://mastodon.thi.ng/tags/WASM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WASM</span></a></p>
Orhun Parmaksız 👾<p>Ratatui started as a terminal UI library... but now it's something else.</p><p>🐁 Meet "**soft_ratatui**" — A pure software renderer backend</p><p>🌐 No terminal or GPU required. TUI everywhere.</p><p>🦀 All powered by Rust!</p><p>⭐ GitHub: <a href="https://github.com/gold-silver-copper/soft_ratatui" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/gold-silver-copper/</span><span class="invisible">soft_ratatui</span></a></p><p><a href="https://fosstodon.org/tags/rustlang" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rustlang</span></a> <a href="https://fosstodon.org/tags/ratatui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ratatui</span></a> <a href="https://fosstodon.org/tags/tui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tui</span></a> <a href="https://fosstodon.org/tags/backend" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>backend</span></a> <a href="https://fosstodon.org/tags/renderer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>renderer</span></a> <a href="https://fosstodon.org/tags/wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>wasm</span></a> <a href="https://fosstodon.org/tags/gamedev" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>gamedev</span></a> <a href="https://fosstodon.org/tags/egui" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>egui</span></a> <a href="https://fosstodon.org/tags/terminal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>terminal</span></a></p>
Thomas Steiner :chrome:<p>Present and Future of Kotlin for Web: <a href="https://blog.jetbrains.com/kotlin/2025/05/present-and-future-kotlin-for-web/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.jetbrains.com/kotlin/2025</span><span class="invisible">/05/present-and-future-kotlin-for-web/</span></a>. Some exciting <a href="https://toot.cafe/tags/WebAssembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WebAssembly</span></a> updates for Web developers wanting to bring their <a href="https://toot.cafe/tags/Kotlin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kotlin</span></a> app (including UI or just the business logic) to the Web through <a href="https://toot.cafe/tags/Wasm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wasm</span></a> and Kotlin Compose Multiplatform.</p>