# Rust Rust is a programming language for building reliable and efficient software. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Migrating the GitHub Copilot runtime to Rust, using Copilot DevFeed: [Migrating the GitHub Copilot runtime to Rust, using Copilot]() Original publisher: [Read original article]() Author: Stephen Toub Published: 2026-09-17T00:26:43Z Content type: article Language: en Sources: [GitHub Engineering]() Topics: [GitHub Copilot](), [Rust](), [Agent Harness](), [GitHub Copilot SDK](), [GitHub]() Tags: [agent-harness](), [ai-agents](), [ai-ml](), [developer-experience](), [generative-ai](), [github](), [github-copilot](), [github-copilot-sdk](), [rust]() ### AI overview The GitHub Copilot agent runtime was rewritten from TypeScript on Node.js and V8 into more than 800,000 lines of production Rust. AI agents wrote most of the code across 128 pull requests, and the runtime was shipped incrementally while regressions were fixed and performance improved by orders of magnitude. ### Source excerpt A rewrite this size wasn't affordable before agents. Here's what porting the Copilot agent runtime to 800,000 lines of production Rust actually took. The post Migrating the GitHub Copilot runtime to Rust, using Copilot appeared first on The GitHub Blog. ## Perplexity's AI agents helped build a database. They weren't allowed to run it. DevFeed: [Perplexity's AI agents helped build a database. They weren't allowed to run it.]() Original publisher: [Read original article]() Author: Amanda Caswell Published: 2026-09-16T21:51:15Z Content type: article Language: en Sources: [The New Stack]() Topics: [Database](), [DynamoDB](), [Rust](), [Artificial Intelligence](), [rocksdb](), [Amazon S3]() Tags: [agents](), [ai](), [ai-agents](), [ai-infrastructure](), [api](), [coding](), [coding-agents](), [database](), [databases](), [dynamodb](), [open-source](), [performance](), [perplexity](), [rocksdb](), [rust](), [s3]() ### AI overview Perplexity built CobbleDB, a Rust key-value store, after finding DynamoDB too costly and insufficiently controllable for its search workload. Coding agents helped develop it, but were not allowed to run it in production. Perplexity measured lower read latency and expects lower costs, with plans to open-source the database. ### Source excerpt Perplexity decided it was paying too much for DynamoDB and wasn't getting the control it wanted over read performance. So The post Perplexity's AI agents helped build a database. They weren't allowed to run it. appeared first on The New Stack. ## Cargo-dyndrv: A new way of building Cargo packages with Nix DevFeed: [Cargo-dyndrv: A new way of building Cargo packages with Nix]() Original publisher: [Read original article]() Author: Ericson2314 Published: 2026-09-16T20:13:36Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Rust](), [systems]() Tags: [announcements](), [blog-post](), [declarative](), [rust]() ### AI overview The article introduces cargo-dyndrv, a new way to build Cargo projects with Nix. It uses dynamic derivations for per-crate incrementality and Cargo's unit graph to align operations with Cargo, while trading some flexibility for fidelity and forward compatibility. ### Source excerpt Obsidian Systems - 16 Sep 26 cargo-dyndrv: A Beginning Building Rust within Nix has always been somewhat of an annoying problem. Nixpkgs includes tools like buildRustCrate to build a single crate and buildRustPackage to build an entire project with all its dependencies, but both have substantial issues:... We have a new way way of building Cargo projects! As the blog post describes, what distinguishes this from all the other ways of building Cargo project in Nix is this combination of methods: Uses dynamic derivations, so no eval time penalty for per-crate incrementality Uses Cargo's unit graph, so we automatically match to how Cargo performs operations Both cargo-dyndrv itself and this blog post about it are all @artemist's work; I am only the one posting it because she has already left for NixCon (see you all there!) and I haven't left yet, so my internet connection is better. Finally, thank you for Saronic for collaborating with us on this project. 6 posts - 5 participants Read full topic ## ClickHouse is now available on the dbt platform DevFeed: [ClickHouse is now available on the dbt platform]() Original publisher: [Read original article]() Author: Aditya Chidurala; José Muñoz; Alex Francoeur Published: 2026-09-16T19:38:40Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Cloud](), [Rust](), [Open Source]() Tags: [adapter](), [announcements](), [beta](), [clickhouse](), [cloud](), [dbt](), [open-source](), [platform](), [release](), [rust]() ### AI overview ClickHouse announces a dbt v2 adapter powered by dbt's Rust engine, available in public beta. ClickHouse is also available as a natively supported data warehouse on dbt Platform in private beta, with support for open-source ClickHouse and ClickHouse Cloud. ### Source excerpt The ClickHouse adapter for dbt v2 is in public beta, powered by dbt's Rust engine. ClickHouse also joins the dbt platform in private beta, supporting open-source ClickHouse and ClickHouse Cloud. ## Translating CUDA Tile Operations from Python to Rust Using Agentic AI DevFeed: [Translating CUDA Tile Operations from Python to Rust Using Agentic AI]() Original publisher: [Read original article]() Author: Tanya Lenz Published: 2026-09-16T16:28:59Z Content type: tutorial Language: en Sources: [NVIDIA Developer](), [NVIDIA Technical Blog]() Topics: [CUDA Tile](), [Rust](), [Agent Skill](), [Artificial Intelligence](), [AI Agent](), [GPU](), [benchmarking](), [Compiler]() Tags: [agent-skill](), [agentic-ai](), [agentic-ai-generative-ai](), [ai-agent](), [benchmarking](), [cuda](), [cuda-tile](), [cutile](), [developer-tools-techniques](), [gpu](), [mixture-of-experts-moe](), [python](), [rust]() ### AI overview This NVIDIA developer article explains a multi-agent workflow for translating cuTile Python and Triton-TileIR GPU kernels into cuTile Rust. The team ported 24 public TileGym operators, covering about 40 kernels, and achieved 99.5% of cuTile Python performance on average, with correctness and performance checks at each stage. ### Source excerpt cuTile Rust (cutile-rs) is a tile-based system for safe, idiomatic GPU kernel authoring in the Rust programming language. Extending the Rust ownership model to... ## Rustls 0.23.45 Released To Fix Two Year Old Security Issue DevFeed: [Rustls 0.23.45 Released To Fix Two Year Old Security Issue]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-14T15:35:11Z Content type: news Language: en Sources: [Phoronix]() Topics: [TLS (Transport Layer Security)](), [Security](), [vulnerability](), [Rust](), [Memory Safety](), [Go Language]() Tags: [bugs](), [desktop-linux](), [go](), [library](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [rust](), [rustls](), [security](), [tls](), [ubuntu-benchmarks](), [ubuntu-hardware](), [vulnerability]() ### AI overview Rustls 0.23.45 fixes a vulnerability in which TLS 1.3 handshake messages sent at the wrong encryption level could be accepted as plaintext after a key-changing message. The issue was present since Rustls 0.23.13 and could allow an on-path attacker to inject plaintext messages, although the authenticated handshake transcript prevented altering or completing the handshake. ### Source excerpt While the Rustls modern TLS library is written in the Rust programming language with a focus on memory safety, as we've seen out of other Rust project re-implementations in the past, the new implementations can lead to other security bugs of their own. Out today is Rustls 0.23.45 to fix a security issue introduced back in 2024 with Rustls while the likes of OpenSSL, BoringSSL, and others are unaffected... ## Security updates for Monday DevFeed: [Security updates for Monday]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-14T13:18:14Z Content type: news Language: en Sources: [LWN.net]() Topics: [Security](), [Debian](), [Fedora](), [Firefox](), [Git](), [nginx](), [Python](), [cURL](), [Elixir](), [F#](), [Redis](), [Rust]() Tags: [curl](), [debian](), [elixir](), [firefox](), [git](), [nginx](), [python](), [redis](), [rust](), [security](), [updates]() ### AI overview Security updates were issued across AlmaLinux, Debian, Fedora, Gentoo, Mageia, Oracle, and SUSE. The affected software includes operating-system components, browsers, developer tools, programming-language packages, servers, libraries, and cloud-related utilities. ### Source excerpt Security updates have been issued by AlmaLinux (389-ds-base, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, kernel, libkcapi, nginx, nodejs:22, nodejs:24, osbuild-composer, perl-YAML-Syck, postgresql16-postgis, ruby, ruby4.0, ruby:3.3, and vim), Debian (jbig2dec, kamailio, nginx, spip, and xorg-server), Fedora (baresip, bind, bluez, bubblewrap, chirp, chromium, cockpit, composer, corosync, darktable, dokuwiki, elixir, exiv2, expat, firefox, freerdp, freerdp2, gdk-pixbuf2, gegl04, golang-x-perf, grpcurl, kernel, kernel-headers, libevent, libmongocrypt, libpcap, libre, libsoup3, memcached, mingw-expat, mingw-openexr, mongo-c-driver, mrtg, nagios-plugins, nsd, nss, openssl, openvpn, PackageKit, pdns-recursor, perl-Net-OAuth, perl-XML-Bare, php-pecl-mongodb2, python-asteval, python-pip, rclone, rest, rust-hickory-net, rust-hickory-proto, rust-hickory-resolver, rust-ppmd-rust, rust-webbrowser, srt, syncthing, tar, tkimg, and valkey), Gentoo (Chromium, Google Chrome, Microsoft Edge, Opera, Vivaldi and Ruby), Mageia (bind, ffmpeg, glibc, java-17-openjdk, java-21-openjdk, librabbitmq, perl-Catalyst-Plugin-Static-Simple, perl-Imager, tor, and xz), Oracle (389-ds:1.4, ansible-core, apr-util, coreutils, freerdp, git-lfs, glib2, gstreamer1-plugins-base, gzip, httpd:2.4, image-builder, java-21-openjdk, kernel, mrtg, nginx, osbuild-composer, perl-DBI, postgresql16-postgis, python-lxml, python3.12-lxml, redis:6, and vim), SUSE (389-ds, ansible-core, ansible-creator, azure-storage-azcopy, cargo-audit, chromedriver, chromium, clamav, containerized-data-importer1.65, containerized-data-importer1.66, curl, dracut, ffmpeg-4, google-guest-agent, google-osconfig-agent, helm, java-1_8_0-ibm, jupyter-nbconvert, kernel, libpng16, libusb-1_0, libvirt, multipath-tools, NetworkManager, opensc, openssl-3, perl-Authen-SASL, perl-HTML-FormHandler, perl-Mojolicious, perl-Protocol-HTTP2, python-jwcrypto, python-sqlparse, python-tornado6, python313-geopy, python313-modelscope ## Back to the Basics. Threads. DevFeed: [Back to the Basics. Threads.]() Original publisher: [Read original article]() Author: Daniel Beach Published: 2026-09-14T12:19:11Z Content type: tutorial Language: en Sources: [Data Engineering Central]() Topics: [Concurrency](), [Rust](), [Concurrent Programming](), [Programming](), [Python]() Tags: [concurrency](), [programming](), [python](), [rust](), [threads]() ### AI overview An introductory, applied discussion of threads and concurrency, focusing on Rust and briefly recalling Python ProcessPools for parallel data and file processing. ### Source excerpt staying grounded in an agentic world ## CPython eases Rust requirements as assimilation continues DevFeed: [CPython eases Rust requirements as assimilation continues]() Original publisher: [Read original article]() Author: Joab Jackson Published: 2026-09-14T10:45:00Z Content type: article Language: en Sources: [www.theregister.com - Articles]() Topics: [Python](), [Rust]() Tags: [devops](), [open-source](), [python](), [rust]() ### AI overview CPython is making Rust an optional requirement, allowing Python developers to benefit from Rust while avoiding the backlash associated with making Rust mandatory. ### Source excerpt By making Rust opt-in, the Python builders hope to enjoy Rust bennies without the backlash that roiled the Linux kernel keepers ## Mold High Speed Linker Being Rewritten In Rust, Hopes To Be The Default Linker On Linux DevFeed: [Mold High Speed Linker Being Rewritten In Rust, Hopes To Be The Default Linker On Linux]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-11T13:21:42Z Content type: news Language: en Sources: [Phoronix]() Topics: [Rust](), [Linux](), [Programming](), [toolchain]() Tags: [compatibility](), [desktop-linux](), [firmware](), [kernels](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [rust](), [speed](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview The Mold high-speed linker is being rewritten from C++ in Rust for Mold 3.0. Its goals include preserving Mold 2.x performance, improving safety, supporting missing linker-script features, and potentially adding incremental linking. ### Source excerpt The Mold high performance linker that typically outperforms the likes of LLVM lld, GNU LD, Wild, and others is being rewritten in the Rust programming language and also has an ambitious goal of being adopted as the default linker on Linux systems... ## Typst 0.15 adds variable fonts, MathML, and multiple bibliographies DevFeed: [Typst 0.15 adds variable fonts, MathML, and multiple bibliographies]() Original publisher: [Read original article]() Author: jake Published: 2026-09-09T15:37:55Z Content type: news Language: en Sources: [LWN.net]() Topics: [Typst](), [pdf](), [SVG](), [Variable Fonts](), [LaTeX](), [Rust]() Tags: [apache](), [features](), [fonts](), [latex](), [new-features](), [open-source](), [pdf](), [rust](), [variable-fonts]() ### AI overview Typst 0.15 adds support for variable fonts, MathML, multiple bibliographies, and other features. The article examines variable-font support and demonstrates it with Roboto Flex and Zycon. ### Source excerpt Typst is a system for typesetting documents into various formats: PDF, SVG, PNG, and, in progress, HTML. It is adept at handling technical material, and is often considered to be an eventual LaTeX replacement. We last looked in on Typst a year ago, when it had reached version 0.13. A new version, 0.15, was released in June with lots of new features, including support for variable fonts, MathML, multiple bibliographies, and more. Typst is free, Apache-2.0-licensed software, programmed in Rust. ## \[$\] Stabilizing Rust's never type DevFeed: [\[$\] Stabilizing Rust's never type]() Original publisher: [Read original article]() Author: daroc Published: 2026-09-08T13:34:38Z Content type: article Language: en Sources: [LWN.net]() Topics: [Rust](), [Compiler](), [Code](), [function]() Tags: [change](), [code](), [compiler](), [error](), [function](), [maintainers](), [optimize](), [rust]() ### AI overview The article explains Rust's never type, denoted by "!", and reports that it was stabilized after more than two years of work. It discusses the feature's practical benefits for optimizing generic code and its role in type inference, while noting a small breaking change to previous Rust editions. ### Source excerpt A function's return type is supposed to indicate the kind of data that it produces. Rust's "never" type, which is denoted by an exclamation mark ("!"), is the type the language uses to mark a function that never returns and other places where a value can never occur. For a long time, the never type was used internally by the compiler, but was considered an unstable feature. On August 24, after more than two years of work, Rust-compiler-contributor "waffle" finally managed to stabilize the type. It took so long, in part, because it involved a small breaking change to previous Rust editions, which the compiler maintainers needed to ensure did not impact much real code. ## Welcome Dongpo and Ross to the Cargo team DevFeed: [Welcome Dongpo and Ross to the Cargo team]() Original publisher: [Read original article]() Author: Weihang Lo Published: 2026-09-08T00:00:00Z Content type: news Language: en Sources: [Inside Rust Blog]() Topics: [Rust](), [Development](), [Caching](), [Testing]() Tags: [2026](), [caching](), [rust]() ### AI overview The Rust Project announces Dongpo Liu and Ross Sullivan joining the Cargo team. Ross is leading the 2026 cross-workspace caching goal, while Eric Huss steps down and Jacob Finkelman and Weihang Lo become Cargo's new co-leads. ### Source excerpt We are excited to welcome Dongpo Liu and Ross Sullivan to the Cargo team! Dongpo has contributed to the Rust Project for years across different teams. He has been an important bridge between Cargo and other Rust teams and has brought insights and fresh ideas from across the Project. Dongpo also integrated cargo info from an external experiment into Cargo as a built-in command. That fulfilled a feature request that was nearly ten years old! He is also a kind and thoughtful reviewer. He always gives careful feedback and takes the time to help contributors. Fun fact: Dongpo joined the team in December 2024, but we never publicly announced it! Ross is brave and a deep thinker. In his first Cargo contributions, he jumped straight into one of Cargo's hardest topics: build artifact management and caching. He has shepherded the new build directory layout through design, implementation, and extensive community testing. This work lays a great foundation for cross-workspace caching and many other future optimizations. He is now leading the 2026 Project Goal for cross-workspace caching! Ross also always takes responsibility for his work. He responds quickly in discussions, fixes regressions, and helps unblock other teams. We are very glad to have him on the team. At the same time, Eric Huss has stepped down from the Cargo team. He contributed to the Rust Project for nearly a decade and served as a Cargo team lead for more than seven years. Eric's fingerprints can be found across basically every part of Cargo. He was our go-to person whenever we needed to understand the history of Cargo. In fact, his work reached far beyond Cargo. He maintained mdBook and books such as the Rust Reference and the Rustonomicon. He also helped lead the Edition work and represented the Dev tools team on the Leadership Council. Cargo and the Rust Project are much better because of him. Thank you, Eric! With Eric stepping down, the Cargo team has selected Jacob Finkelman and Weihang Lo as its new co-l ## Rust debugging survey 2026 results DevFeed: [Rust debugging survey 2026 results]() Original publisher: [Read original article]() Author: Sam Kellam Published: 2026-09-07T00:00:00Z Content type: article Language: en Sources: [Rust Blog]() Topics: [debugging](), [Rust](), [ide](), [Command-line interface]() Tags: [2026](), [command-line](), [debugger](), [debugging](), [developers](), [ide](), [rust](), [survey]() ### AI overview The Rust project reports results from its first Rust Debugging Survey, which received more than 2,300 responses. The article examines who uses debuggers, how Rust developers debug programs, and the debugging challenges they encounter. More than 46% of respondents currently use debuggers, while print debugging and the macro are widely used, followed by debugging inside an IDE and on the command line. ### Source excerpt One of the biggest challenges Rust developers report in our annual surveys is a subpar debugging experience. So, back in February, we ran our first Rust Debugging Survey, in the hopes of identifying how Rust developers are using debuggers and what problems they are facing when doing so. We received over 2,300 responses, and we'd like to thank everyone who took the time to participate in the survey! In this report, we'll go over some of the results of the survey. If you'd like, you can also check out the complete results of the survey. If you'd like to skip ahead to any particular section, you can do so with this index: Who Uses Debuggers? How Are Debuggers Used? Challenges Debugger Visualizers Closing Remarks Who Uses Debuggers? The first step to making sense of the survey results is understanding who took the survey. We asked respondents to rate their Rust expertise, from "Never used it" to "Advanced". Over 80% reported themselves as "Advanced" or "Intermediate", split roughly evenly between the two: [PNG] [SVG] We also asked respondents if they currently use or have used debuggers in Rust. Over 46% said they currently do, with the remaining responses split between "have in the past" and "never have". That means that over half of respondents do not currently use a debugger for Rust! [PNG] [SVG] Categorized by expertise, the responses reveal that roughly half of "beginners" have never used debuggers in Rust! On the other hand, nearly half of "advanced users" currently do use debuggers in Rust: [PNG] [SVG] For respondents who indicated they had previously used Rust but no longer did, we asked if challenges with debugging support were why they stopped. For nearly 3%, the answer was "yes", with an additional 24% reporting debugging issues as being partially responsible (though mind the small response count; most respondents were active users of Rust): [PNG] [SVG] How Are Debuggers Used? Knowing what debuggers developers are using and how is another important part of un ## Latent Powers DevFeed: [Latent Powers]() Original publisher: [Read original article]() Author: Armin Ronacher Published: 2026-09-05T00:00:00Z Content type: opinion Language: en Sources: [Armin Ronacher]() Topics: [Dongle](), [Hacking](), [Rust](), [Embedded Software Dev](), [Protocol (disambiguation)](), [Raspberry Pi]() Tags: [ai](), [dongle](), [firmware](), [hacking](), [protocol](), [raspberry-pi](), [rust](), [soc](), [thoughts](), [usb]() ### AI overview A developer experiments with modifying a cheap CarPlay dongle to run custom code while preserving regular CarPlay functionality. After receiving a different SoC than expected, they use LLM-assisted discussions to flash the device and compile CatPlay, a Rust reimplementation of the CarPlay protocol, for the hardware. ### Source excerpt A few weeks ago I felt like it would be fun to see if I can make one of those cheap Chinese CarPlay dongles run something other than the stock firmware. The idea was that rather than just forwarding CarPlay, why not do something more interesting with them? They all work quite similarly: they act as bridges between your car and the phone. From there they deal with video and audio streams and pass some other data through. Most of them also bring up a custom UI for pairing and have a web interface that your phone can reach for updates. Long story short: I had a conversation with Fable and Sol via Pi about what could be done with such a dongle or whether I should use a Raspberry Pi instead if I wanted to do my own thing there. I figured it might be quite fun to run my own code while still allowing regular CarPlay to pass through. Through working with the LLM I learned about CatPlay, which is a Rust reimplementation of the CarPlay protocol that can run on Carlinkit devices. In particular, it can run on the Carlinkit Mini Ultra, which I figured would be easy enough to buy. I do have a few CarPlay adapters around, but I did not have that particular model, so I bought one on Amazon. Twenty-four hours later, I had a device in my hand that was branded as a Carlinkit Mini Ultra, but instead of being the Ingenic device that the original author used, it turned out to be something else. This is normally where the story would stop. However, it's 2026. Armed with a bit of knowledge about how these systems work, I managed to have some fruitful discussions with Kimi K3 and Sol and figure out how flash the device and in turn, how to make CatPlay compile for that SoC. I guess that hacking these USB devices is not necessarily hard, but it's laborious and you can easily end up bricking your devices. It also just sucks because sometimes you need to work with someone else's code that does not itself run on your machine. In the past, I would abandon many such projects for lack of tenacity. ## Shehab Amin on Spark Compatibility, Rust, and LakeSail DevFeed: [Shehab Amin on Spark Compatibility, Rust, and LakeSail]() Original publisher: [Read original article]() Author: Daniel Beach Published: 2026-09-02T12:22:23Z Content type: article Language: en Sources: [Data Engineering Central]() Topics: [Apache Spark](), [Rust](), [data-engineering](), [apache-arrow](), [agentic-coding]() Tags: [apache-arrow](), [apache-spark](), [data-engineering](), [rust]() ### AI overview A podcast conversation with LakeSail co-founder and CEO Shehab Amin about Spark compatibility, Rust, Apache Arrow, DataFusion, and data infrastructure. It also discusses data-stack choices, streaming and batch processing, agentic coding, and using existing data pipelines as a basis for AI pipelines. ### Source excerpt Data Engineering Central Podcast. ## 1.98.1 pre-release testing DevFeed: [1.98.1 pre-release testing]() Original publisher: [Read original article]() Author: Release automation Published: 2026-09-02T00:00:00Z Content type: release Language: en Sources: [Inside Rust Blog]() Topics: [Rust](), [releases](), [Release notes]() Tags: [pre-release](), [release](), [rust](), [testing](), [update]() ### AI overview The Rust 1.98.1 pre-release is ready for testing and is scheduled for release on September 3. The article provides instructions for trying it locally and links to release notes and feedback channels. ### Source excerpt The 1.98.1 pre-release is ready for testing. The release is scheduled for September 3. Release notes can be found here. You can try it out locally by running: RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable The index is https://dev-static.rust-lang.org/dist/2026-09-02/index.html. You can leave feedback on the internals thread. General feedback about our pre-release process is welcome on this GitHub issue. ## A Self-Baked Async FFI Framework for Rust C# Interop DevFeed: [A Self-Baked Async FFI Framework for Rust C# Interop]() Original publisher: [Read original article]() Author: Cynthia Dunlop Published: 2026-08-31T13:00:34Z Content type: article Language: en Sources: [ScyllaDB]() Topics: [Rust](), [Tokio](), [.NET](), [C#](), [scylladb](), [For the Love of Code]() Tags: [c-sharp](), [drivers](), [engineering](), [hackathon](), [interop](), [rust](), [scylladb]() ### AI overview The article describes ScyllaDB's effort to build a Rust-based driver architecture with thin language-binding layers, focusing on a C# driver. It explains the motivation for creating a custom asynchronous FFI framework to connect Rust's Tokio runtime with .NET's async runtime over the C ABI, after existing binding-generation tools proved insufficient for Rust-C# async interoperation. ### Source excerpt How we got tokio and .NET's async runtime talking to each other, over the C ABI ## Program management in July-August 2026 DevFeed: [Program management in July-August 2026]() Original publisher: [Read original article]() Author: Nurzhan Saken Published: 2026-08-31T00:00:00Z Content type: article Language: en Sources: [Inside Rust Blog]() Topics: [Rust]() Tags: [2026](), [funding](), [infrastructure](), [project](), [rust](), [update]() ### AI overview The Rust project's July-August 2026 program-management update reports seven newly opened goals, one completed goal, two discontinued goals, and changes in goal funding. It also covers project updates, repository and Zulip channel renaming, improved goal-owner reporting, configurable reminder frequency, and automatic Zulip topic creation for proposed goals. ### Source excerpt It's been fun since the last update. Tomáš was away for a month, and I had to get my wisdom teeth pulled right after he left. Despite everything, a lot has happened! Project Goals Since the previous update, we've opened seven more goals: Contracts: primitive ownership assertions Process-Safe Rustup Toolchain Operations End-to-End Executable Rust Specification f16b Primitive Type Polymorphic code generation experiment C interop: Complex Allocators 1.0 There's now a roadmap for Binary size reduction, which includes async future and statemachine optimization goals, build-std, and future possibilities that aren't goals yet. One goal was completed (Stabilize Cargo's linting system), and two were discontinued (Experimental language specification and Continue Experimentation with Pin Ergonomics). Several goals have received partial funding (Incremental Systems Rethought, Native async fn dynamic dispatch in traits, and Cargo cross workspace cache), and some are now fully funded (C interop: f80, f128, and c_longdouble, C interop: Complex, and Async statemachine optimization). Don't forget to add your goal to the funding table if it needs funding (see template)! Some goal owners and contributors have been writing about their work beyond the regular goal updates. Here are some of the places to check out: Monthly updates by Hexcat Rust Maintainer Monthly Report: August 2026 by Gen Li Status Update - July 2026 by the BorrowSanitizer team Field Projection Designs by Benno Lossin Four levels of in-place initialization by Yoshua Wuyts Optimizing the new trait solver by Jana Dönszelmann Rust Function Overloading - Call for Experimentation by teor A Vision for a Rust Formal Specification by Nadrieril Infrastructure The Goals repository has been renamed to rust-lang/goals from the verbose rust-lang/rust-project-goals, and we've renamed the Zulip channels to #goals, #goals/proposed, and #goals/meta. The website now lives at goals.rust-lang.org; the old links should redirect there ## Type-Safe Authentication in Rust with Auth0 and Axum DevFeed: [Type-Safe Authentication in Rust with Auth0 and Axum]() Original publisher: [Read original article]() Author: Aniket Bhattacharyea Published: 2026-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Auth0 Blog]() Topics: [Authentication](), [Auth0](), [Rust](), [Command-line interface](), [OAuth 2.0](), [Authorization](), [API]() Tags: [api](), [auth0](), [authentication](), [authorization](), [cli](), [oauth](), [oauth-2-0](), [rust](), [tokens](), [tutorial]() ### AI overview A tutorial showing how to build a Rust CLI that uses Auth0's OAuth 2.0 Device Authorization Flow, then create an Axum API that validates the resulting access token before allowing access to a protected route. ### Source excerpt Secure your Rust CLI applications with Auth0 Device Code flow and protect your Axum backend endpoints by validating JWTs with Rust's type safety. ## Electing new Project Directors 2026 DevFeed: [Electing new Project Directors 2026]() Original publisher: [Read original article]() Author: Manish Goregaokar Published: 2026-08-28T00:00:00Z Content type: article Language: en Sources: [Inside Rust Blog]() Topics: [Rust]() Tags: [2026](), [process](), [project](), [rust]() ### AI overview The Rust Project has launched its 2026 process to elect two Project Directors to the Rust Foundation Board. Project members are invited to nominate candidates by September 21, with the election following candidate gathering. ### Source excerpt Today we are launching the process to elect two Project Directors to the Rust Foundation Board of Directors. This is the fourth round of slots, following from last year's election. We will briefly explain the goals and procedures here, but this is mostly copy-pasted from last year's post and the official process documentation. We ask all Project members to begin working with their Leadership Council representative to nominate potential Project Directors. See the candidate gathering section for more details. Nominations are due by September 21. What are Project Directors? The Rust Foundation Board of Directors has five seats reserved for Project Directors. These Project Directors serve as representatives of the Rust Project itself on the Board. Like all directors on the Foundation board, the Project Directors are elected by the entity they represent, which in the case of the Rust Project means they are elected by the Rust Leadership Council. Project Directors serve for a term of two years and will have staggered terms. This year we will appoint two directors and next year we will appoint three directors. See the role description document for more details about what is involved in being a Project Director. The current Project Directors are Carol Nichols, David Wood, Jack Huey, Niko Matsakis, and Ryan Levick. This year, Carol Nichols and Ryan Levick's seats are up for reelection. We want to make sure the Project Directors can effectively represent the Project as a whole, so we are soliciting input from everyone on the team. The elections process will go through two phases: 1) candidate gathering and 2) election. Read on for more detail about how these work. Candidate gathering The first phase is beginning right now. In this phase, we are inviting the members of all of the top level Rust teams and their subteams to nominate people who would make good Project Directors. The goal is to bubble these up to the Council through each of the top-level teams. You should be heari ## How we saved 100 terabytes of memory by optimizing 1.1.1.1's DNS cache DevFeed: [How we saved 100 terabytes of memory by optimizing 1.1.1.1's DNS cache]() Original publisher: [Read original article]() Author: Sebastiaan Neuteboom Published: 2026-08-27T17:02:35Z Content type: article Language: en Sources: [Cloudflare Blog]() Topics: [Cache](), [Caching](), [Cloudflare](), [Rust](), [benchmarking](), [Latency](), [datacenter]() Tags: [1-1-1-1](), [benchmarking](), [cache](), [cloudflare](), [data-center](), [deep-dive](), [dns](), [engineering](), [latency](), [memory](), [net-maui](), [optimization](), [performance](), [rust]() ### AI overview Cloudflare describes five Rust-level changes to the memory layout of Big Pineapple, the platform behind 1.1.1.1 and other DNS services. The changes reduced DNS cache entry size by over 50%, freed roughly 100 terabytes of memory across the fleet, increased insert throughput by 43%, and reduced lookup latency by 19%. ### Source excerpt Five Rust-level memory optimizations to the DNS cache layout of Big Pineapple cut per-entry memory by 56%, freeing approximately 100 TB of memory across Cloudflare's fleet. ## Announcing our first Maintainers in Residence DevFeed: [Announcing our first Maintainers in Residence]() Original publisher: [Read original article]() Author: Lori Lorusso, Jakub Beránek Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Rust Blog]() Topics: [Rust](), [Maintainers](), [Amazon Web Services](), [Google](), [OpenAI]() Tags: [aws](), [blog](), [contributors](), [google](), [maintainers](), [openai](), [rust](), [support]() ### AI overview The Rust Project announces its first Maintainers in Residence and Maintainer Grant recipients, with funding for at least 12 months through the Rust Foundation Maintainers Fund. The article explains the program's support categories, selection process, and focus on strengthening critically underfunded, high-impact Rust teams. ### Source excerpt We are very happy to announce the Rust Project's first round of Maintainers in Residence: Gen Li (@rami3l), Chris Denton (@ChrisDenton), Alejandra González (@blyxyas), León Liehr (@fmease), and Maintainer Grant recipients: Jason Newcomb (@Jarcho) and Jonas Böttiger (@joboet). These contributors will be funded for their rust-lang maintenance activities for (at least) the following 12 months! The funding of the Maintainer in Residence (MiR) and Maintainer Grantee roles is possible thanks to generous donations to the Rust Foundation Maintainers Fund (RFMF) from Google, AWS, OpenAI, the Rust Project Leadership Council and also individual sponsors. We also want to thank the people who advocated for maintainer funding within their companies; Tyler Mandry from Google, Niko Matsakis and Jess Izen from AWS and Predrag Gruevski from OpenAI, and also the whole Rust Leadership Council and our funding advisors. If you would like to help us support even more Rust contributors, consider donating to RFMF. The Rust Foundation has published a press release and a blog post, where you can learn more about the sponsors and the supported contributors. Read more below to learn about the MiR program, how we chose the funded contributors, and of course who they are! Background The Maintainer in Residence program, established in RFC 3931, is designed to provide stable financial support for Rust contributors, so that they can truly focus on crucial maintenance activities. Currently, there are three categories of support that we offer: Full-time MiR: funded for 5 days/week of Rust Project work Half-time MiR: funded for ~2.5 days/week of Rust Project work Maintainer Grant: funded for ~1 day/week of Rust Project work Funding for this program comes from the Rust Foundation Maintainers Fund, which was launched recently, and the whole program is managed by the Rust Funding team. When deciding who to fund, we took a systematic approach. First, we looked at Rust teams to understand their maintenance ## Intent to Ship: JPEG XL DevFeed: [Intent to Ship: JPEG XL]() Original publisher: [Read original article]() Author: Jake Archibald Published: 2026-08-24T15:32:15Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Firefox](), [Web](), [Rust](), [Firefox Nightly](), [Google](), [Chrome](), [C++]() Tags: [blog](), [browser](), [browsers](), [c-plus-plus](), [developer](), [features](), [firefox](), [firefox-nightly](), [google](), [hacks](), [interop](), [mozilla](), [uncategorized](), [web]() ### AI overview Mozilla announces its intent to ship JPEG XL in Firefox, using Google Research's Rust-based jxl-rs decoder to provide secure, performant support. The article highlights progressive rendering and compares JPEG XL with AVIF for different image-compression use cases. ### Source excerpt It isn't often that new image formats land in browsers. In the early 2000s we had JPEG, GIF, and PNG. The 2010s gave us WebP, which was a modest step up from JPEG. But the 2020s have given us two new image formats that are a big step up from previous formats: AVIF and JPEG [...] The post Intent to Ship: JPEG XL appeared first on Mozilla Hacks - the Web developer blog. [Next page]()