I've been meaning to take a look at the #Rust language for a while now. Thanks to @liw I've taken the first steps on that journey.

I suspect it'll be a while yet before I give up my C compiler, but Rust has a lot more to it than just "memory safety".

Thanks Lars!

https://blog.brettsheffield.com/rust-with-lars

#Rust

Alt...

Four panels in the style of the Anakin and Padme meme: First panel: Ferris the Rust crab, happy with arms raised, saying “If your code compiles, then it works” Second panel: Me, slightly smiling, saying “And it does compile, right?” Third panel: Ferris, arms down, blank expression Fourth panel: Me, looking slightly more serious, repeating “And it does compile, right?”

Wanted: a #RustLang tool with 4 panes:
- desired generated code
- an in progress proc-macro being written
- input #Rust code where the proc-macro is being applied
- a live updating view of the actual generated code with diff annotations against what was desired

If you want to go fancier, tie things in the output to the input and provide suggestions on where things are missing pre-expansion for the output to march the expectation. I feel like 90% of this can be accomplished today with tmux+a file watcher+direct rustc invocations using -Zunpretty=expanded, but it'd be lovely to have an actual tool for this.

This episode of #OpenSourceSecurity I chat with @tb about crates.io trusted publishing

I learned a ton about how trusted publishing works, it's one of those very new and very interesting topics

And of course anytime I can talk about #Rust it's a great chat :)

https://opensourcesecurity.io/2025/2025-08-cratesio-trusted-publishing-tobias/

- Software engineer/developer
- Preference for 3rd shift, but if I can work anywhere, I'll find a place to live to fit your schedule.
- holistic software development("full stack")
- References out the wazoo, especially from my most recent position.
- Any language, but I'm practiced in Java, #cpp , HTML, CSS, like #rust , and have professional exp. in Java, SQL, PL/SQL, and BASH
- English, #日本語 , #suomi , Français, et Español.

#getfedihired #nonprofit #opensource

@nixCraft @BastilleBSD #bash, #guile and #rust is all I need.

Plus a tall mast and good wind....

What are the challenges and gains when porting legacy systems software written in C into #Rust? Here's my own experience porting the BSD Unix / macOS stream editor sed into Rust as part of #uutils.
IEEE Software article: https://doi.org/10.1109/MS.2025.3579008
Source code: https://github.com/uutils/sed/

What is the idiomatic way in #Rust of defining a type that represents an MMIO region and therefore must use volatile loads and stores for every field access?

I did a RIIR again and:

Two apps nearly-identical in functionality now. On startup, before processing anything:

#Rust + #Axum: 3.5MB RES
#Elixir + #Phoenix: 75MB RES

Literally 20x difference, and I haven't even benchmarked throughput/perf. For a use case where a big goal is extremely low resource use, this is huge.

(both of these are running in release/prod mode btw)

Dist users: 0.29.0 is out! This has all the features that originated in Astral's fork, and also has some new bugfixes and other improvements. https://github.com/axodotdev/cargo-dist/releases/tag/v0.29.0

#rust

Does #Rust have any kind of property syntax like C# / Objective-C (or that you can fudge with proxies in C++), so I can write a.property = value and have a method called to set the property?

Wrote a short blog post on how I implement command line interfaces in Rust these days.

https://blog.liw.fi/posts/2025/rust-cli/

#RustLang #Rust #CLI #commandLineInterface

Teaching Rust is fun.

#Rust #RustLang

Exciting to see the first #Rust code running on #CHERIoT! Edoardo has rebased the Kent work on a newer rustc and added the CHERIoT bits so we can now add two integers together in Rust!

Probably other things work too. The core library compiles, but not much of it is tested. Cross-compartment calls aren’t possible yet and the alloc crate needs implementing wrapping our shared heap (there’s also a fun project at UBC to replace our allocator with a formally verified one in Rust, but it’s not there yet and, of course, depends on Rust working).

#JavaLand in Europapark? Super-Saver-Price? Well, more like a rewrite in #Rust… I won't #Go.

Netencode: I’m currently building out my project of making a “better” structured language for use in UNIX-pipelines and shell scripting and the like.

It’s human-readable, but supports trivial generation with printf & wc, tagged values (sum types, Result<T>) and embedding arbitrary binaries without escaping due to being length-prefixed.

I think it’s pretty cool!

#netencode #ShowAndTell #unix #shell #haskell #python #rust #nix #programming #tooling

Alt...

An excerpt from early in the readme, showing some json to netencode tools and environment integration

Alt...

An example of a pretty-printed netencode structure, with a bunch of record fields and nested metadata

The fuck?

#rust

Alt...

use std::io::Read; fn main() { let mut buffer = [0; 1024]; let stdin = std::io::stdin(); let mut handle = stdin.lock(); println!("Calling read() directly..."); match handle.read(&mut buffer) { Ok(0) => println!("Read 0 bytes (EOF)"), Ok(n) => { println!("Read {} bytes: {:?}", n, String::from_utf8_lossy(&buffer[..n])); } Err(e) => println!("Error: {:?}", e), } }

Alt...

● Bash(echo "t5:hello," | ./simple_read) ⎿  Calling read() directly... Read 10 bytes: "t5:hello,\n" ● Bash(./simple_read < /tmp/test_simple.ne) ⎿  Calling read() directly... Read 0 bytes (EOF)

Created a FreeBSD port for openpgp-card-tools and put it on my Codeberg:

https://codeberg.org/Larvitz/openpgp-card-tools-freebsd-port

It's a command-line-utility (oct), written in Rust, to manage openpgp smartcards and compatible devices (yubikey, nitrokey etc).

Usage instructions are in the repositories readme file.

#freebsd #openpgp #rust #port @hko

@cy as a rust hater, if I was a compiler writer, I would seriously consider learning Rust and writing a Rust compiler for the latest version of the language, in C.

Just because current tools are too huge, as you note here. #lang_en #rust

Hello #rust people 🦀

Am I correct in my understanding that to use or manage rust crates I would need a #GitHub login?

Looking at crates.io and this github issue[1] from 2016 it seems that using Microsoft's GitHub is the only way to login or publish. Is that still the case?

I'm rather reluctant to go back to using GitHub having given up GitHub[2] some years ago.

[1] https://github.com/rust-lang/crates.io/issues/326

[2] https://sfconservancy.org/GiveUpGitHub/

#GiveUpGithub

First time using "cargo mutants" and am happy with it.

#Rust #RustLang

@spacehobo @brouhaha @tastytronic

Talking of cool formats:

I was just thinking of Rahul Dhesi's ZOO after posting that, coincidentally.

The format was designed so that backwards seeks were only necessary when actually deleting/updating entries. One could do a list entirely forwards, and even purging deleted entries could be done entirely forwards.

Then the world went and settled on ZIP, which needed several backwards seeks just to find the central directory.

One has to appreciate that #Rust programmers are rediscovering all of these old problems anew almost 40 years later. (-:

https://github.com/zip-rs/zip2/pull/197

#ZIP #ZOO #magtape #Unix #archivers