Today was my last day at my current workplace where I wrote performant #Rust BE code for a personal healthcare solution. It has been really fulfilling writing Rust in my day job, but now it is time for me to move on from oxidizing personal healthcare to giving back GPs' time with #Typescript. I look forward to starting at my new, exciting workplace very soon. Stay tuned!
In the meantime, I'll be putting my Rust skills to work building a new personal project which involves #wasm. 👨🏽💻
New note on my website:
> Lately I've been spending time learning Scheme and using it to implement the concepts I'm learning in my physics classes as time permits. One of the most exciting things I've been doing with this is getting my Scheme to compile to the Web thanks to Hoot.
Lately I've been spending time learning Scheme and using it to implement the concepts I'm learning in my physics classes as time permits. One of the most exciting things I've been doing with this is getting my Scheme to compile to the Web thanks to Hoot. One of the biggest challenges has been the fact that Hoot is unstable. It's currently at version 0.9.0. The documentation is decent, but it could be better. The error messages can be cryptic. But it's a massive accomplishment to see Scheme code running on the Web via WASM. It's even more incredible to know that it's running on a stack the team created themselves, not relying on Emscripten. My initial understanding of Hoot was that it could compile any Guile program to the Web. I quickly learned that I was mistaken when my code wouldn't compile. I then ported my code to use the Hoot versions of all of the functions, causing my code to be unable to run independently from Hoot. I then realized that Hoot actually supported more of Guile than I thought. I just had to manually import a lot of the stuff I previously took for granted. Now I have set up my code to run on native Guile and on WASM via Hoot, with tests automatically running in both to make sure everything's set up correctly for both environments. It's a bit of a pain, but it works now. Most of my code is agnostic to whether it's running with the system's Guile interpreter or if it's been compiled to WASM and being run in the browser. I think that's amazing. Currently, most of the work I've done has been on the backend. Working on getting this whole setup to work at all has been a hassle. I've also been working on getting the more fundamental physics logic working, which is especially difficult as a someone new to Scheme. But I've been making progress, and I've published a small prototype on a new page on my website and have published the source code. In the future I'm curious to see if it's reasonable to compile Zig + Scheme programs to the Web with Hoot. I'm starting to feel more and more that Zig + Scheme is the perfect combination and I want to do more experimentation in that direction. That may be too complicated! I don't know yet. There's a lot for me to learn in the WASM world, and that's a large part of the fun. This has been an insightful exploration into the depths of Scheme. I can't wait to do even more.
Nice. @hetzner added a proof of work bot protection to their accounts subdomain that requires me to enable WASM.
WTF 
I definitely won't do that. So no more access to my servers. Noice.
That is definitively the wrong way of doing a bot protection.
New Blogroll Post
“Embedding user code in your app using Extism” by Thejesh GN
@thej: «Every application I love has some kind of power-user mode where I can add my own code or scripting to make it useful to me. Simple examples are Firefox with its addons or VLC with its plugins.…»
#Technology #Architecture #FreeAndOpenSource #PowerUser #WASM #WebAssembly #blog #indieweb https://thejeshgn.com/2026/05/19/embedding-user-code-in-your-app-using-extism/?ref=blr.indiewebclub.org
Execution engine review: this one is long because ELF loading, WASM runtime behavior, binary loading, JIT paths, traps, and portability can introduce a lot of subtle kernel bugs.
This post looks at what still needs to be implemented before the execution engine should be pushed through the final dev cycle, after the architecture and abstraction layer.
How do you handle portability testing near the end of an OS dev cycle?
#Wasm #KernelDev #SystemsProgramming
https://oreulius.com/blog/code-review-the-wasm-runtime-and-elf-execution-engine
electromagnetic Stellavlinder⭐
Abraham Samma🔬🔭 🇦🇺🇹🇿
Anna Liberty
lmorchard's links
Lukas Rotermund
Indieweb Club Bangalore
Kevin McDonald
Kevin McDonald
Oreulius Kernel
Lobsters [Unofficial]