Debugging Rustler on Illumos by @dziban https://lobste.rs/s/nr8kkd #elixir #illumos #rust
https://system-illumination.org/01-rustler.html

#kanidm #idm #rust #proxmox #identitymanagement #opensource #oauth #oidc #ldap #authentik #virtualization #howto

https://gyptazy.com/blog/kanidm-with-proxmox-and-oidc-the-full-setup/

Every day, I"m thankful that transitive library tracing installers exist: #freebsd pkg(8) and #debian apt-get. I stared on #slackware and remember being awed by RedHat's `rpm`.

But...

How is it that installing `gnustep-base` gets me a #rust compiler, a #tex installation, #ruby (<3 you forever), #python, and #perl (because why leave any interpreted language behind?); oh wait, there's #lua too. This is not reasonable.

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

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

✨ cargo-semver-checks v0.43.0 is out ✨

This release cycle focused on making it a joy to use and build. We improved performance on large crates, cut down our CI time, tackled a large rustdoc JSON format migration, and paid down technical debt.

Enjoy!
https://github.com/obi1kenobi/cargo-semver-checks/releases/tag/v0.43.0

#rust #rustlang #semver

Alt...

v0.43.0 - In this release - Spotlight: I'm giving a talk at Rust Forge! - Performance improvements - 1 new lint, for a total of 178 This release requires Rust 1.87+ both to install (MSRV) and at runtime. Future releases will require Rust 1.88+. Spotlight: I'm giving a talk at Rust Forge! Rust Forge is a creative new conference organized by Rust in Action author Tim McNamara. It's scheduled for 27-30 August 2025 in Wellington, New Zealand. My talk is titled "The Past, Present, and Future of SemVer in Rust" and I'm extremely excited about it! Here's a short description: At least 1-2 times per week, accidental breaking changes sneak into the new release of some popular Rust package, despite the maintainers' best efforts. Why is this still a problem 10 years after Rust 1.0? What will it take to finally stop such breakage, so we can have fearless cargo update? It's not too late to grab a ticket! I hope to see you there!

Alt...

Performance improvements Supporting an exponentially-growing number of lints requires periodic maintenance in the form of mandatory performance engineering, Without it, things would quickly get out of hand, and large crates and large workspaces would be affected first. To prevent that, this release cycle focused on both internal and external improvements. Externally-visible improvements include lint execution time improvements, courtesy of a new query profiling tool prototype developed by @CLIDragon. This allowed us to add targeted new indexes that speed up the execution of some lints by as much as 10x! After these optimizations, running the full suite of lints on Rust's largest crates needs only ~2s, down from around ~8s previously. Internal improvements include a variety of optimizations aimed at reducing the time taken by our CI suite, from an original of ~7min for cargo test down to around ~1min. If you're wondering why cargo test used to take 7min in the first place: our test suite runs ~250000 lint queries to ensure correctness and keep false-positives out! Even extremely cheap operations done 250k times add up very quickly! After the optimizations, we still run those 250k queries — we didn't sacrifice correctness at all, but merely cut out avoidable overhead. New lints We added only one new lint in this release, tracking an additive-only API change: enum_must_use_removed. This lint group remains opt-in-only.

@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?

Today I wrote about 300 lines of Rust featuring "unsafe" that I thought about quite carefully.

Then I started adding safety comments. The act of needing to convincingly argue that something is true made me find and fix 3 bugs I had missed before.

Safety comments exist for a reason!
#rust #rustlang

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

I think there is a Dunning–Kruger like effect whereby the complexity of rewriting an open source project from scratch is vastly underestimated the less you know about the scope of the work.

You could make 80% of #inkscape in a couple of months of javascripting. But this is 80% of Inkscape's surface. Not actual depth.

Rewrite it all in #Qt? #React? #JS? #Rust? These are ideas aren't bad. But they are vast projects that would cost millions of dollars.

Related to: https://mastodon.uno/@maxdid/114691504835360868

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).