First screen, captured 5 days ago.

2026 is an exciting year for the Rust compiler (and me)

What HN thinks

A celebratory compiler roadmap post, promptly turned into a support group for people with 190GB target directories.

Build times and disk usage hurt
Many commenters say slow compiles and huge target directories are Rust's real pain points, citing 15-20+ minute builds. Others reply that such builds point to bad setups, heavy generics and macros, or bloated vibe-coded dependency trees.
Excited for new trait solver
Commenters welcome the new solver and polymorphization work as overdue fixes to technical debt. They hope it unblocks specialization and async features like Return Type Notation.
Rust isn't the endgame language
One camp predicts a simpler, faster-compiling, safe successor language. Others counter that Rust is already everywhere, or that OCaml and other GC languages already fill that role.

Consensus: Most agree Rust compiles slowly and eats disk space, and that careful crate structure and dependency hygiene matter a lot. They disagree on how much of the blame falls on the toolchain versus the codebase.

Recommended in the comments

OCaml (other): Suggested as an existing safe language with fast build loops, and defended as usable for low-latency systems code.
cargo-hakari (tool): Suggested for getting more reuse of compiled dependencies and less target bloat.
rust-glancer ↗ (tool): Suggested for people struggling with rust-analyzer's RAM usage.
TinyGo ↗ (tool): Cited as evidence that GC languages can work on tiny hardware.
Typed Racket (other): Offered as an answer to wanting a Lisp with strong type safety.
Coalton (other): Also suggested as a Lisp with Rust-like type safety.

Summarised by Claude from the comment thread 3 days ago.

Points: 166
Comments: 117
Posted: 2026-10-20 by panstromek
Category: Programming

rust rust-compiler trait-solver type-systems compilers

All captures:

Looks similar

Screenshot of yoyo-code.com: Why is GitHub UI getting slower?

Why is GitHub UI getting slower?(yoyo-code.com)

137 points by lr0 1 year ago | 67 comments

Screenshot of joshuamo876.bearblog.dev: Can Rust Beat JavaScript in 2023?

Can Rust Beat JavaScript in 2023?(joshuamo876.bearblog.dev)

53 points by stmblast 3 years ago | 90 comments

Screenshot of steveklabnik.com: I see a future in jj

I see a future in jj (steveklabnik.com)

318 points by steveklabnik 1 year ago | 224 comments

Steve Klabnik's blog post explaining why he believes the jj (Jujutsu) version control system has a future, drawing parallels to his early bet on Rust.

jj jujutsu version-control git