HN Top 10 — May 05, 2026
Today’s Top 10 on Hacker News
1. Async Rust never left the MVP state
⭐ 170 💬 82 👤 pjmlp 🔗 Discuss on HN
I’ve previously explained async bloat and some work-arounds for it, but would much prefer to solve the issue at the root, in the compiler. I’ve submitted a Project Goal, and am looking for help to fund the effort. I love me some async Rust! It’s amazing how we can write executor agnostic code that can run concurrently on huge servers and tiny microcontrollers.
2. Should I Run Plain Docker Compose in Production in 2026?
⭐ 48 💬 30 👤 pmig 🔗 Discuss on HN
I am Philip—an engineer working at Distr, which helps software and AI companies distribute their applications to self-managed environments. Our Open Source Software Distribution platform is available on GitHub (github.com/distr-sh/distr) and orchestrates both Docker Compose and Docker Swarm deployments on customer hosts every day. Most of the production incidents I have seen on Docker Compose hosts come…
3. Bun is being ported from Zig to Rust
⭐ 537 💬 376 👤 SergeAx 🔗 Discuss on HN
Bun’s team is porting the runtime from Zig to Rust in a two-phase approach. Phase A produces a draft .rs file next to each .zig that captures the logic faithfully — it doesn’t need to compile yet. Phase B wires up Cargo.toml and makes each crate compile. The porting guide bans popular Rust async libraries (tokio, rayon, hyper, async-trait); Bun owns its own event loop and syscalls. No async fn is allowed — everything stays as callbacks + state machines, matching the Zig original.
4. Empty Screenings – Finds AMC movie screenings with few or no tickets sold
⭐ 162 💬 130 👤 MrBuddyCasino 🔗 Discuss on HN
Empty Screenings Empty Screenings About 10% of AMC movie showings sell zero tickets.
5. Lessons for Agentic Coding: What should we do when code is cheap?
⭐ 73 💬 59 👤 ingve 🔗 Discuss on HN
10 Lessons for Agentic Coding May 4, 2026 DEVELOPMENT 10 Lessons for Agentic Coding What should we do when code is cheap? Lately, this blog has featured a lot of writing about agentic coding. Frontier models are really good at coding these days, much better than they are at other tasks.
6. Hand Drawn QR Codes
⭐ 122 💬 21 👤 jollyjerry 🔗 Discuss on HN
Hand‑drawn QR codes — Seth Larson Hand‑drawn QR codes Seth Larson @ 2025-07-01 I really like QR codes. Recently I purchased a new sticky-note-like pad from a new local stationery store in Minneapolis. The sheets have a 10x10 grid and 2x10 grid.
7. When everyone has AI and the company still learns nothing
⭐ 12 💬 0 👤 youngbrioche 🔗 Discuss on HN
What changed because we spent those tokens? And who moves discoveries from individuals to teams to organizational capabilities? Robert Glaser 05 May 2026— 9 min read !Image 2: When everyone has AI and the company still learns nothing Ethan Mollick has been…
8. Google Chrome silently installs a 4 GB AI model on your device without consent
⭐ 288 💬 287 👤 john-doe 🔗 Discuss on HN
Two weeks ago I wrote about Anthropic silently registering a Native Messaging bridge in seven Chromium-based browsers on every machine where Claude Desktop was installed [1]. The pattern was: install on user launch of product A, write configuration into the user’s installs of products B, C, D, E, F, G, H without asking. Reach across vendor trust boundaries.
9. How OpenAI delivers low-latency voice AI at scale
⭐ 410 💬 129 👤 Sean-Der 🔗 Discuss on HN
Voice AI only feels natural if conversation moves at the speed of speech. When the network gets in the way, people hear it immediately as awkward pauses, clipped interruptions, or delayed barge-in. That matters for ChatGPT voice, for developers building with the Realtime API, for agents working in interactive workflows, and for models that need to process audio while a user is still talking.
10. CVE-2026-31431: Copy Fail vs. rootless containers
⭐ 113 💬 48 👤 averi 🔗 Discuss on HN
rootless containers - Andrea Veri’s Blog CVE-2026-31431: Copy Fail vs. After that post went out I spent the weekend setting up a lab to actually run the exploit, trace it at the syscall level, and verify that the rootless Podman architecture we deploy on GNOME’s runners would contain it. This post documents the entire process: from disassembling the shellcode to watching the kernel reject the privilege escalation in real time.