New week, new Rust! What are you folks up to?
Just finished implementing support for version 3.0 of the WebAssembly specification in my parser.
I'll be following up with various QoL improvements and polishing the library, hopefully making it more useful for folks working with Wasm modules at the binary level.
2 Likes
Still working on my Adobe Brush converter. The format is almost completely decoded but now I am going crazy mapping source (.abr) brush properties to Krita ones (and generating the XML that included in the preview PNG is the real brush). I really need an artist with competences in both Photoshop and Krita to help me...
3 Likes
I “finished” BTreeSet for my pstd crate, am now thinking about what to do next. Maybe Vec?
2 Likes
Continuing to implement some more clusters for my ZCL library.
Currently: Illuminance Level Sensing
1 Like
I recently picked up and largely finished a project to convert rustdoc-json into a more human-usable form, with the intention of making alternate docs viewers. To that end, I'm currently working on a basic framework to facilitate just that.
2 Likes
I’ve been experimenting with Rust in embedded systems, particularly integrating it with FreeRTOS on small IoT boards. I revisited the Rust Embedded Book while working through task scheduling and no_std constraints:
I also found this walkthrough of running Rust + FreeRTOS on the PADI IoT Stamp interesting from a practical integration standpoint:
Still I am confused about how Rust abstractions behave under RTOS scheduling and tight memory conditions. This is my goal for the next week.
1 Like
Can I ask you why FreeRTOS and not something a bit more modern like Zephyr?
1 Like
Just added the missing 7° (8 block) slope to arrie - GTA2 map viewer using bevy - which makes the map rendering almost complete.
I also started to make koppeln - a minimal self-hostable dynamic DNS server - compliant to the minimal requirements for a DNS server. It's an old project of mine and will need a lot of refactoring, too.
1 Like
I am on my learning journey and want to understand multiple platforms.
I'd like to share the CLI I built in a weekend called Fuelcheck CLI: GitHub - chasebuild/fuelcheck-cli: 
Lightweight command-line utility designed to monitor and manage token consumption across the modern AI ecosystem..
Lately, there’s been a significant surge in AI agent usage, so I decided to write a lightweight version of CodexBar (created by @steipete, the father of @openclaw) called Fuelcheck CLI.
In short, it works exactly like CodexBar, allowing agent users to track token consumption and real-time costs directly within the terminal.
Key Features:
- Broad Support: Currently compatible with Codex, Claude, Gemini, Cursor, Kimi/Kimi 2, Factory Droid, http://z.ai, and various other cloud agents.
- Terminal-Native: Lightweight and designed to stay out of your way while you work.
I hope this proves useful for everyone!