What's everyone working on this week (52/2025)?

community
1

New week, new Rust! What are you folks up to?

1 Like
2

Reverse engineering the .abr format continues. I have the "samp" section fully done for version 6.2 and I can extract the full property tree from the "desc" section. Next the patterns section and eventually a public release of at least the parser. The full tool that converts to krita brush format will require some more work.

1 Like
3

A blazingly fast (:"D) concurrent ordered map... I posted about this last week too.. but this week there are concrete results from pretty rigorous benchmarks that seem very promising for actually continuing this project. Actually seems to be outperforming both std BTreeMap and other popular alternatives (I won't claim this to be fully accurate as I am still working on making the benches more fair) I was quite surprised that there was no high perf concurrent ordered map crates available. I would highly appreciate it if someone familiar with concurrent data structures takes a look at it (repo)

NOTE: It was originally started as a port of the Masstree implementation in C++, but I diverged so much from it that I am not sure that it would be accurate claiming so. Especially because I changed the whole memory reclamation model from epoch based to hyaline based. Also yes, AI usage here and there, especially for adding tests, logs, build scripts etc. But most of the core code and design was written by me O.O

1 Like
4

Adding spectrum analysis to MuTate. Architecturally, support mapping single audio input (the monitor stream) to multiple output streams. Also working on feedback rendering and looking for places to apply my personal ML tricks.

I would say open issues on MuTate if you want to work on it. Honestly, just find pub fields that can be private and make it so. We will be copying some features of scope-tui to work on the offscreen rendering. Integrating music into Hyperland window decorations requires the same frontend decoupling and will bring in a ton of users.

The "making your money smarter" side of PrizeForge is in development. The underlying tech will completely change how social networks are built and used. We will apply that to socially deciding how to earmark and spend funds. The MVP will probably be something even simpler just to demonstrate the UI and get early feedback. Expecting this to last a few weeks.

5

I'm working on Byte Heist, a site where you can solve coding challenges in different programing languages including Rust.

The async process libraries availible didn't support custom numbered pipes so for one dependency I needed an entirely custom AsyncProcess implementation (on top of the nix crate, at least it didn't need to be cross-platform), which then necessitated an entirely custom implementation of async pipes.

This has led me to a weeks long hunt to track down every race condition, deadlock, and infinite loop my users have found. I had no idea how async in Rust worked at the low level but now I am "more than familiar" with the intricacies (otherwise known as traumatized by all the pitfalls).

6

As my second Rust project, I'm writing a parser for Wasm modules (more accurately, a binary format decoder): GitHub - agis/wadec: A WebAssembly binary format decoder

It can be used either as a CLI or as a library. It passes all the official test suite, so I'd say it's conformant to the spec (v2). My aim is to focus on DX, helpful errors and diagnostics and solid docs.

It's still in very early stage and I'm pretty new to the language, so any feedback is more than appreciated!

2 Likes
7

I have experimented with MNIST (handwritten digits). Managed to push Hinton's Forward-Forward algorithm to 99.29% accuracy using a Rust implementation. I added dropout and "symmetric augmentation" to the training mix, which he didn't in his original paper.

Used Rayon for parallelisation (matrix multiplication), but no other major dependencies - like ndarray or torch.

1 Like
8

  • Still trying to figure out how to implement TLS ServerHello and further a WebTransport server using only Web API's shipped in the browser.

  • Added support for 64 MiB input from the browser for Node.js Native Messaging host.