How Our Rust-to-Zig Rewrite is Going For the past year and a half, the team building Roc's compiler has been rewriting our 300,000 lines of Rust code into Zig, for reasons I'll recap below. We recently passed an exciting milestone: feature parity with the original compiler! Since the Bun project recently shared an experience report of their rewrite in the other direction (from Zig to Rust, althoug
8× faster binary search: from compiled code to mechanical sympathy by Itamar Turner-Trauring Last updated 18 Jul 2026, originally created 11 Jul 2026 How do you speed up computational Python code? A common, and useful, starting point is: Pick a good algorithm. Use a compiled language to write a Python extension. Maybe add parallelism so you can use multiple CPU cores. But what if you need more spe
A kernel with most of what Linux 0.11 had — processes, virtual memory with demand paging and CoW fork, the Minix v1 filesystem, ATA disk driver, VGA + PS/2 console, 8250 serial console, TTY layer, signals, and the complete syscall table. A Rust user-space "std" — user_lib mirrors the public shape of std::{fs, io, path, env, process, time} so user programs read like ordinary Rust, not like syscall
homewritingClosing a three-year-old issue using Rust arenasI am part of the core team working on Gleam, a small, friendly functional programming language written in Rust. A little while ago I ran into a three-year-old issue suggesting how we could start using arenas to make the language's pretty printer faster. Quite ominously the issue ends with: "This would be quite a long manual job." That soun
There has been a lot said about error handling in rust. There are many different opinions about how to structure your errors, when to use panics, and the role of proc-macros in error handling. Most of the discussion around rust error handling makes the assumption that when an error occurs you either pass the error up to the caller or you try to completely recover and continue on. While this descri
The Images service, built in Rust on Workers, runs on every machine in Cloudflare’s edge network. To handle client connections, we use hyper, an open-source HTTP library for Rust. Last year, we introduced the Images binding to enable custom, programmatic workflows for processing remote images in Workers. At the end of 2025, we rearchitected the binding to provide a more direct, local connection be
Free, forever. AGPL-3.0, no paid tier, no account, no token. 100% conformance per implemented service. Every operation validated against AWS's own Smithy models — 59,000+ generated test variants on every commit. Tested against upstream Terraform acceptance tests. CI runs hashicorp/terraform-provider-aws TestAcc* suites against fakecloud. Catches waiter/field-presence/drift bugs that pure SDK tests
(These 27 are the large repos that are slow enough to time meaningfully; the full accuracy suite is 52 repos — see below.) Median per-repo speedup ~85×; the aggregate is higher because pylint's duplicate-code check (R0801) is O(n²) and dominates on test-heavy repos like black. These are single-core numbers — the inference engine is single-threaded to replicate astroid's order-sensitive global cach
Bevy 0.19Posted on June 19, 2026 by Bevy Contributors Thanks to 261 contributors, 1185 pull requests, community reviewers, and our generous donors, we're happy to announce the Bevy 0.19 release on crates.io! For those who don't know, Bevy is a refreshingly simple data-driven game engine built in Rust. You can check out our Quick Start Guide to try it today. It's free and open source forever! You c
A modular 64-bit Unix-like kernel written in Rust about The kernel is written in (almost) 100% Rust and attempts to avoid unsafe code where possible. It implements a big range of POSIX APIs in system calls, but also exposes common extensions found in Linux and BSDs, like epoll and timerfd. This allows it to run a somewhat modern desktop using Wayland and X11 sessions. Most drivers are implemented
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
