Ralith

@ralith.com

Software developer working with open source, transport protocols, gamedev, hypervisors, etc.

usa: we forgor to sandbox our automated hacking bot and it hacked ppl lol. scary as fuck. you should give us more money about it china: we made a humanoid robot that can run straight into a wall and fucking die faster than any previous humanoid robot could run straight into a wall and fucking die

this is a great idea! on dreams we did something similar: replays were a png of the screen at start of recording, with the serialised save state after and then packet record. explorer et al just ignored the extra data :) crash dump handler wrote the same format, so every crash bug came with a

I feel like game devs are a unique combination of all of “doing some of the hardest software engineering”, “wild west cowboy bullshit”, and “hitting themselves in the head with hammers for no reason”

Oh, this is cool! New rust-analyzer command. "rust-analyzer: Evaluate Predicate" Then type in the type and bound and it'll tell you whether it holds. So, you don't have to go through source code anymore. #rustlang

PropertyInfo<u32>: Unpin
> predicate holds

i know the point of the "soda bottle next to a stack of sugar cubes" visualization is to shock you with how much sugar they cram into sodas but the takeaway i get from it is more like "oh cool i can just eat a fuckload of sugar cubes and it wouldn't be worse than having a soda"

This new graviola release is amazing! aws-lc-rs v1.17.0: 18 dependencies - 16s release build rustls-graviola v0.3.4: 45 dependencies - 9s release build rustls-graviola v0.4.0: 19 dependencies - 5.5s release build Tested on a 24 vCPU 5950X VM. github.com/ctz/graviola...

Release 0.4.0 · ctz/graviola

A new ML-KEM-768 implementation using verified assembler from the mlkem-native project. This drops the dependency on libcrux-ml-kem from rustls-graviola and the crate feature. Runtime performance i...

github.com

I thought it would be fun (or at least interesting) to do some FAQs and answers on the #RustLang consulting I offer (I have availability from pretty much now, if this sounds useful)...

I hate to join the error handling hot takes but I really wish we'd settled on a convention for the `Display` formatting of `Error` (that is, whether it runs recursively or whether you're expected to follow the `source`). A mix a both styles leads to intensely overly verbose error prints.

NixOS is the only system where I can hand someone a file and they get *my* machine. it's also the only one where a one-line change can eat 12GB of RAM mid-build and take the session with it. both things are true. I keep using it anyway. make of that what you will.