I've gotten a new laptop from work, which I was planning to set up (my first @tuxedocomputers laptop, an #IBP15 <3 ) and mid-installation I realised:

I really need to clean up my #dotfiles So I started an intensive modernizing project, including migrating to #chezmoi During which I realized:

My #git Integration in #zsh was always a bit broken, and also a bit slow, and it would be really good to clean up that part of my configuration.

So I started another project. I am now three levels deep in project what should have just been an @archlinux installation on a Tuxedo laptop 😅. Hope I don't fall into the next level while coding 🙈

But hey, I now have my first two real code repositories, exclusively on @Codeberg and my first real @rust project!

- https://codeberg.org/pygospa/dotfiles
- https://codeberg.org/pygospa/vcs-prompt

#projectmanagement #timemanagement #coding #programming #rust #refactoring #modernization

It's probably about time I got another job.

I'm a Senior Software Engineer, with experience in large scale, high-throughput back-end systems.

I'll put my hand to most things, but I've most recently been doing #Erlang, Kubernetes, etc. at a gambling company.

Strongly prefer remote. London, UK.

Visceral loathing of GenAI and LLMs.

I've recently been messing around with Elixir and Phoenix. I would potentially like to move into #Rust.

My "me" page is at https://rogerlipscombe.me/

#GetFediHired

rust-lang/rust is adopting an LLM policy

If you personally use LLMs and want to contribute to the Rust toolchain, you *really* should read it.

The summary is "It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to *create*." Effectively, no other human should see LLM output, unless they ask for it, and LLM usage shall be disclosed.

https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langrust-is-adopting-an-llm-policy/

#RustLang #Rust

I’m a Rust compiler maintainer looking for full-time remote employment　involving Rust-related open-source work.

While I’m currently employed as a Staff Software Engineer, I’d like my next role to include time for upstream Rust　compiler contributions.

I’m based in Kyoto and am not looking to relocate, but I can travel　occasionally.

Introductions and boosts would be appreciated.

https://tako8ki.com/posts/looking-for-a-new-role

#rust #opensource #getfedihired

I'd like to release my clingwrap crate as 1.0.0. As part of that, made some tidying up and added logging. This means I'll want to wait at least a month to see the changes are good.

clingwrap is my helper crate for building command line programs: load config files (JSON, TOML, YAML, XDG), run programs (std::process::Command, but nicer error type), and a bit more. I wrote it for myself, and use it a lot, but maybe it is useful for others, too?

https://crates.io/crates/clingwrap

#Rust #RustLang

The next one in the #peoplebehindosco series is Felix.

Hi @Gronner 👋

Felix is a software engineer with more than 10 years experience in the automotive and medical industry. Working at XITASO he focuses on building secure and safe systems. Besides that he provides trainings on security, safety, software architecture and Rust. To learn in and with a community he organises the SWEC and is a member of the iSAQB. He loves learning by exploring: building small embedded system or tools, mostly in Rust. In his spare time he enjoys playing pen & paper games, miniature figure painting and playing the drums.

His Tags: #AppSec, #Embedded, #Rust, #ThreatModeling

Thank you very much for your work as a volunteer and your support in organizing the Open Security conference. Stay tuned and follow the hashtag #peoplebehindosco for more people behind osco.

Successfully ported the complete #LLVM stack (version 19.1.7, including llvm's binutils, clang, ldd) to #Solaris 11 Express (snv_151a) #SPARC. This build of #Solaris works on #SPARC machines that Solaris 11 GA (and later) do not support (example: sun4u workstations and servers), as well as machines that #Illumos does not support completely. This may allow for #Zig and #Rust to be ported to this version of Solaris on SPARC. Complete source archives, build instructions, and signed binaries in SVR4 package format (and soon, IPS) will be available for download. #Solaris #SPARC #retrocomputing #Illumos #Sunmicrosystems

CC: @ptribble @SolarisDiaspora

Candidature rejetée, après deux entretiens, parce que l'entreprise «s'oriente vers une adoption forte de l'IA dans ses pratiques de développement, une direction qui ne semble pas alignée avec vos attentes à ce stade».

Est-ce qu'il y a encore des éditeurs de logiciels en France qui sont prêts à embaucher un développeur qui préfère écrire lui-même son code ?

#GetFediHired #Rust #Scala #Python #PostgreSQL

@cks

That's messed up.

I made the mistake of looking at the #Debian source tree first, to see how this is happening. This is no help, and I couldn't figure out how the dependency was getting in there from list2depends, substvars, and whatnot.

Because it turns out that this was an explicit bodge, only in #Ubuntu, made in September of 2025.

https://git.launchpad.net/ubuntu/+source/build-essential/commit/?id=28bd47593db15e492a66bd2531ad8caeb76f0caa

Temporary for nearly a year, so far. (-:

#coreutils #rust-coreutils

Time for some shameless self-advertisement: I have some availability starting this September!

I'm an experienced OSS maintainer, with lots of work done on @doctrine and @getlaminas

I push for #DDD (with humans & tactical).

Languages mostly #Go, #PHP, although I'd love to do some #Rust, and I read anything at all.

I can #Terraform your infrastructure, work on hardening CI/SA pipelines, Docker and #Nix builds, test suites.

Rates between 700~1100 EUR/day depending on terms. #getfedihired

Rewriting Bun in Rust, by @jarredsumner (@bun.sh):

https://bun.com/blog/bun-in-rust?ref=frontenddogma.com

#refactoring #bun #rust

So the bad news is I have been laid off.

The good news is that I'll have a lot more time to write in the short term, both book stuff and code stuff.

...anyone need a #rust programmer?

I had a chat with Lori Lorusso and Niko Matsakis about the Rust Foundation Maintainers Fund

Funding open source is a huge topic right now, the Rust Foundation has some great ideas. It will be exciting to watch this one grow and evolve

https://opensourcesecurity.io/2026/2026-07-rfmf-lori-niko/

#OpenSourceSecurity #rust #RustFoundation

RE: https://mastodon.social/@CuratedHackerNews/116848267418783428

... Like #rust? Missing something I guess.
It still uses npm?

ok! it was a fever dream week of rushed readme-driven #Rust development, but finally I have something for you all to test out. :)

the new #SparkleShare CLI codenamed Twinkle:

https://github.com/hbons/Twinkle

#linux #foss #OpenSource #git #GitHub #GitLab #CodeBerg

Woah, check this!
I came across this easy mistake to miss in #Rust!
Modern Rust is so tricky!
Luckily the Rust Geesechecker stopped me from pushing this to production and forgetting to value the #Goose.
Here we can see on line 190 I clearly forgot to value the goose, which would have resulted in a catastrophic market segmentation fault!
Luckily the #Rust compiler knows that the true source of value is the Golden Egg factory inside the #goose

Alt...

error[E6005]: use of unvalued goose: `goose` --> src/main.rs:192:24 | 189 | fn internal_mechanism(asi: &mut sb::ASI) { | -- value miscalculation occurs because type `Egg` does not implement the `Lay` trait 190 | let mut _goose = asi.goose_mut(); | ^ goose was not valued here 191 | 192 | let egg = _goose.lay(); | ^^^ egg laid here after move warning: unvalued variable: `goose` --> src/main.rs:190:9 | 190 | let _goose = asi.goose_mut(); | ^^^^^^ help: if this is not intentional, remove the prefixed underscore: `goose`

I'm very interested in systemic solutions to problems. Blaming an individual when they make a mistake *feels* reasonable. When a significant percentage of people make the same mistake (70%, 2%, it doesn't matter as long as it is measurable, predictable and has a negative impact), then it's *not* a persons fault.
We know how to tackle those kind of problems: we change the environment to minimize the likelihood of mistakes. Traffic and pedestrian safety is an example of a well explored space where we know what works. Bollards, narrower streets, slower speeds, raised pedestrian crossings, providing good alternatives to driving to reduce traffic...
Similar in industrial spaces: clear signaling, segregate heavy machinery from human limbs, clear and practiced process to get out of dodge when things go poorly...
It's always about looking for solutions to eliminate mistakes, and when they can't be eliminated, minimize the blast radius.
This is why I like #Rust: it's a language and tooling that applies the industrial approach of "if two people make this mistake, figure out how to mitigate it".
We can't "individual responsibility" our way out of systemic problems.
I want more software with bollards.

Machine Learning with Rust, Second Edition: Implement data pipelines, classical models, deep learning and NLP using burn, candle, linfa and smartcore by GitforGits | Asian Publishing House is a new release on Leanpub!

Link: https://leanpub.com/rustmachinelearning

#books #ebooks #newreleases #leanpublishing #selfpublishing #machine_learning #deep_learning #neural_networks #large_language_models #ai #rust

Rust From the Ground Up by M Provost is on sale on Leanpub! Its suggested price is $39.99; get it for $24.74 with this coupon: https://leanpub.com/rust-from-the-ground-up/c/LeanPublishingDaily20260618 #computer_programming #rust

RE: https://mastodon.social/@rustaceans/116755672316463652

yserver

― a modern X11 server written from scratch in Rust.

<https://github.com/joske/yserver>

"… there are multiple projects on GitHub with this name (but none for X11 servers), the name is subject to change. …"

<https://lobste.rs/s/yy8je0/yserver_modern_x11_server_written_from>

<https://www.phoronix.com/news/YSERVER-Rust-X11-Server>

"… can currently run a full MATE, Xfce, or Cinnamon X11 desktop. The prominent X11 extensions from RandR to DRI3, GLX, MIT-SHM, Composite, and others are supported. And, yes, with working Compiz goodness too:

… open-source under an MIT license. …"

<https://news.ycombinator.com/item?id=48531394>

<https://www.reddit.com/r/linux/comments/1u31shc/comment/or1re0p/>

#AI #Linux #X11 #yserver #Rust

Rust for Javascript Developers: A Practical Guide to Systems Programming for the Web Developer by Dwayne Charrington is a new release on Leanpub!

Link: https://leanpub.com/rustforjavascriptdevelopers

#books #ebooks #newreleases #leanpublishing #selfpublishing #software #rust #computer_programming #javascript

Rust for Linux Programming: Build kernel modules, drivers, file systems, networking, and memory using Rust's ownership, traits, and RAII by GitforGits | Asian Publishing House is a new release on Leanpub!

Link: https://leanpub.com/rustlinuxprogramming

#books #ebooks #newreleases #leanpublishing #selfpublishing #rust #algorithm #compiler #systemsengineering #data_structures

New blog post: Do-the-work instead of proof-of-work, for Git hosting

https://blog.legoktm.com/2026/06/14/do-the-work-instead-of-proof-of-work-for-git-hosting.html

On https://git.legoktm.com/ I am now running a fully client-side Git repository viewer; on the server-side it is entirely static hosting, which makes it super cheap.

I hope this is a useful proof-of-concept as an alternative to (IMO wasteful) solutions like Anubis and provides better user privacy in the process.

#Git #WebAssembly #Rust #SelfHosting

Verification complete with a successful result!

My next project will be a #Radicle orchestrator process that can mirror our repos to third-party resource (like our read-only presence on GitHub).

While I find #Rust easy to read, I haven't written much #Rustlang code yet. This will be a good exercise in learning Rust. :-)

The main idea is to implement bunches of features in this orchestrator (the first being the aforementioned repo mirroring support.) The next feature will likely be per-commit emails and issue/patch notifications via #Pushover.

TIL the --locked argument to 'cargo install', necessary to workaround upstream breakage in the time crate causing bob to fail, and looks like lots of others:

https://github.com/time-rs/time/issues/783

Doesn't seem great that a broken publish of an indirect dependency can break so much software, and there was much WTFing while trying to explain why a build that worked yesterday didn't work this morning.

Why isn't --locked the default?

#rust #rustlang #bob

Learn Zig over Rust and C++: Learn Modern Systems Programming with Zig for C++ and Rust Developers by GitforGits | Asian Publishing House is a new release on Leanpub!

Link: https://leanpub.com/zig-rust-systemprogramming

#books #ebooks #newreleases #leanpublishing #selfpublishing #rust #c_and_cpp #systems_engineering #game_development #computer_hardware #graphics

Rust In Practice, Third Edition: Concurrency, Memory Safety, GPU Computing, Linux Kernels, and Real-World Systems using Rust 1.85 by GitforGits | Asian Publishing House is a new release on Leanpub!

Link: https://leanpub.com/rust2026

#books #ebooks #newreleases #leanpublishing #selfpublishing #rust #agentic_engineering #computer_hardware #embedded_systems #graphics #c_and_cpp

Not sure who decided it was a good idea to integrate Rust dependencies into Python modules.

Installing a 1GiB Rust package to build wheel is a waste of bandwidth and time.

#FreeBSD #Python #Rust #WHY

Alt...

x Preparing metadata (pyproject.toml) did not run successfully. | exit code: 1 > [5 lines of output] /tmp/pip-build-env-4onzua_e/overlay/lib/python3.11/site-packages/setuptools/_vendor/wheel/bdist_wheel.py:4: FutureWarning: The 'wheel' package is no longer the canonical location of the 'bdist_wheel' command, and will be removed in a future release. Please update to setuptools v70.1 or later which contains an integrated version of this command. warn ( Python reports SOABI: cpython-311 Unsupported platform: 311 Rust not found, installing into a temporary directory [end of output]

This might be controversial, but no matter where you sit at the #AI #slop #rsync debate, the best thing you can do is to write tests for all the recent regressions.

No matter if you want to constrain rsync more, improve #openrsync or #gokrrsync, or vibe up another rsync in #Rust, tests will help you achieve this, and they use a different skill set from just writing code.

When you compile #Rust code within a #ghostty window, you get a native percent bar are the top of the window 😎