This Week in Rust Issue 645 Rounds Up April 2026 Community News

Canonical's announcement that ntpd-rs will become Ubuntu's default time synchronization daemon, replacing chrony, linuxptp, and gpsd in a single memory-safe binary, is the kind of signal that does not stay buried in a GitHub thread for long. Issue #645 of This Week in Rust surfaced it front and center, making it the standout headline of the April 1 digest. Below are the five items from this issue that deserve hands-on time this weekend, ordered not by importance but by how quickly you can act on them.

Crate of the Week: tsastat

Thread-level profiling on Linux has always required piecing together perf output, custom scripts, or kernel tracing tools that assume you already know what you are looking for. tsastat changes that calculus. Suggested by Ankur Rathore, this week's featured crate is a high-resolution Thread State Analysis (TSA) tool built for Linux, designed to give you a structured picture of exactly what your threads are doing and when. If you write or maintain latency-sensitive Rust services on Linux and have ever stared at a CPU flamegraph wondering why a thread is stalling without obvious cause, tsastat is the direct path forward. Start with `cargo install tsastat`, point it at a running process, and let the TSA output reframe your profiling workflow. It matters right now because async Rust systems are increasingly going to production, and the observability gap between a flamegraph and actual thread-state data is where hours disappear.

Blog Post Spotlight: "Ntpd-rs: It's About Time!"

The most consequential Rust production story in this issue is the announcement that Ubuntu is adopting ntpd-rs as its default time synchronization client and server across upcoming releases. The Trifecta Tech Foundation develops ntpd-rs as part of Project Pendulum, a full-featured implementation of both the Network Time Protocol and Network Time Security written entirely in Rust. Canonical's plan is phased: ntpd-rs lands in Ubuntu 26.10 for testing, then graduates to the default in Ubuntu 27.04. The implementation already runs in production at Let's Encrypt, where it replaced the previous NTP daemon in June 2024 without incident. For systems Rust programmers, the blog post published on the Ubuntu Community Hub is worth reading end-to-end: it traces why memory safety matters specifically for time sync (TLS certificate validation and distributed system consistency both depend on accurate, tamper-resistant clocks), and it outlines how ntpd-rs consolidates three separate Ubuntu tools into one. This follows earlier Rust system-component adoptions at Canonical, including sudo-rs and uutils coreutils. The direction is unmistakable.

Conference CFP: EuroRust 2026 - Barcelona, April 27 Deadline

EuroRust returns to Barcelona this October, running from October 14 through October 17, and the call for papers closes April 27. That gives you 26 days from issue publication date to submit a talk. EuroRust consistently draws an audience of practitioners rather than observers, which means the bar is not a polished keynote but a concrete problem solved with Rust and an honest account of what it took. If you have been shipping production Rust, exploring async runtimes, contributing to a crate, or hitting interesting compiler edge cases, that is a talk. Submit through the EuroRust CFP process and tag your submission via a PR to TWiR or by reaching out on Bluesky or Mastodon if your event needs additional amplification. NDC Techtown in Kongsberg, Norway also has an active CFP for its September conference window, making this a strong month for anyone considering a first conference submission.

Compiler Performance: Query System Gets Faster

Issue #645 includes the weekly compiler performance triage, and the picture this week is mixed but meaningful. Infrastructure troubles prevented some rollup PRs from generating their standard "unrolled" builds, which complicated regression investigation. The team, triaged by @kobzol across revision range 6f22f613 to cf7da0b7, was able to locate and revert the largest rollup regressions before they landed in stable. The notable upside: PR #154304 delivered concrete improvements by optimizing the query system. If you track compile times across large workspaces, the query system is where incremental compilation pressure concentrates, and targeted improvements here compound across codebases at scale. The full performance report is linked in the issue for anyone who wants to dig into the artifact comparison numbers.

Community This Week: In-Person Meetups and a Hackathon

Three community events land in the April calendar this issue. The San Diego Rust Meetup returns in person after a recent virtual run, the Rust LA group is back for its April session, and Oxidar.org is hosting a hackathon called Snakear, pitched as a come-hack-with-Rust event open to participants at any level. The Oxidar event is particularly useful for anyone looking for a structured environment to build something new rather than maintain something existing. If you are in these regions, the calendar links are in the issue; if you are running a Rust event elsewhere, the standard path is a PR to TWiR or a message on Bluesky and Mastodon.

One More: The Quote Drought

Issue #645 ends with a quiet plea. Quote of the Week reads: "When you do cursed things, problems find you." And then a note from curator llogiq that four consecutive weeks have passed without a community suggestion. TWiR's quote section is one of the smallest parts of the digest and one of the most human: it collects the kind of offhand wisdom that surfaces in issue threads and forum replies and would otherwise vanish. If something you read this week said something true about writing Rust, that is a submission. The process is a PR away.

TWiR #645 lands at a moment when Rust's production footprint is expanding faster than its educational infrastructure can track. ntpd-rs in Ubuntu, tsastat for thread visibility, a Barcelona CFP ticking down: each item in this issue connects to that broader shift. The digest earns its place in a weekly reading routine precisely because it compresses those signals into a single, skimmable document that keeps the community moving in the same direction.