RE: https://hachyderm.io/@rain/117446589082698170

See this update:

RE: https://hachyderm.io/@rain/117446083340236126

Update: Nick G. from Anthropic has responded on HN, and I believe that the attribution is now sufficient. I stand by my posts as of the time I wrote them.

https://news.ycombinator.com/item?id=50107559

Discuss on Hacker News: https://news.ycombinator.com/item?id=50106738

Update on my post from yesterday. I am significantly less measured this time: https://sunshowers.io/posts/anthropic-mononoke-2/

Discuss on Hacker News: https://news.ycombinator.com/item?id=50094694

New blog post: https://sunshowers.io/posts/anthropic-mononoke/

just released port-file on crates.io -- if you tell a child process to bind a service to port 0, facilities for the child to tell the parent what port it actually bound to. A very simple problem solved very well

https://docs.rs/port-file

context: upcoming nextest version will let you run `cargo nextest help repo-config`, `cargo nextest help user-config`, etc, and render the config reference in the terminal. akin to man pages that also work on Windows

nerds:

(1) if you don't use `less`, what pager do y'all use?
(2) does your pager support OSC 8 hyperlinks?

Apologies for the late notice, but Rust Bay Area meetup is THIS EVENING in SF! Come join us

https://luma.com/2ppjzpyr

We love Rust for how much the compiler helps enforce safety. But sometimes it's up to us to uphold the complex--and often unclear--expectations of what constitutes safety on our own. Oxide colleague, @rain, joined me and @bcantrill to talk about the technical details of what it takes to impose safety on the hardest type of unsafe Rust.

https://youtu.be/mdcu3dKMjyg

RE: https://hachyderm.io/@rain/116681245175413548

ICYMI, @rain had a terrific blog entry last week -- and today, she joins @ahl and me on Oxide and Friends to discuss the blog entry, the work behind it, and the reaction to it. Join us, 5p Pacific today!

https://discord.gg/QrcKGTTPrF?event=1513573369495421038

iddqd, or the hardest kind of unsafe Rust.

My first post for the @oxidecomputer
blog! Goes deep into the pitfalls of unsafe Rust and how to reason about it. A lot of labor went into the post -- please have a read!

https://oxide.computer/blog/iddqd-unsafe

We're hosting a Rust meetup in SF, WEDNESDAY April 15. Join us!

https://luma.com/2vpan32j

Read more about how the RustRover IDE supports nextest:

https://blog.jetbrains.com/rust/2026/04/03/rustrover-2026-1-professional-testing-with-native-cargo-nextest-integration/

Going to be doing a livestream about cargo-nextest with the JetBrains folks -- Wed April 8, at 10:00 PDT/17:00 UTC. Please register if you're interested!

edit: due to sickness this was postponed — will post the new date as it's finalized!

https://info.jetbrains.com/rustrover-livestream-april9-2026.html

Bay area peeps -- we're hosting an East Bay #rustlang meetup on the 18th! Come join us in downtown Oakland, steps away from BART :)

https://luma.com/cyu67mpz

Published the design document for how nextest implements records, replays and reruns. It's very large — over 6000 words! Lots of decisions and alternatives considered, to make what I believe is the best implementation of this set of features in the industry. Have a look!

https://nexte.st/docs/design/architecture/recording-runs/

Microsoft Productivity Pack for Windows (1992)

I have just been informed that on github, windows CI actions are performed in an environment where C:\ is mounted as a -network- drive.

Which means that the default temporary directory location, normally found on C, is a remote block device.

Which means that every tempfile interaction requires a network transaction to complete.

Which means that github CI actions take -significantly longer to do- and are -more expensive for their operations- than they have to be.

Which has the consequence that -your- cost for github CI actions is greater than it has to be, because those profiteering fucks charge by the minute.

https://docs.github.com/en/billing/concepts/product-billing/github-actions