Backpropagation is a leaky abstraction
karpathy.medium.com
Notes by djb on using Fil-C (2025)
cr.yp.to
Visopsys: OS maintained by a single developer since 1997
visopsys.org
How I use every Claude Code feature
blog.sshh.io
Why do AI models use so many em-dashes?
seangoedecke.com
Claude Code can debug low-level cryptography
words.filippo.io
Crossfire: High-performance lockless spsc/mpsc/mpmc channels for Rust
github.com
Updated practice for review articles and position papers in ArXiv CS category
blog.arxiv.org
Hyperbolic Non-Euclidean World (2007)
web1.kcn.jp
CLI to manage your SQL database schemas and migrations
github.com
LM8560, the eternal chip from the 1980 years
tycospages.com
GHC now runs in the browser
discourse.haskell.org
The Naked Man Problem and the Secret to Never Forgetting Numbers
ninjasandrobots.com
Chip Hall of Fame: Intel 8088 Microprocessor
spectrum.ieee.org
Anonymous credentials: rate-limit bots and agents without compromising privacy
blog.cloudflare.com
Show HN: Why write code if the LLM can just do the thing? (web app experiment)
github.com
Automatically Translating C to Rust
cacm.acm.org
SQLite concurrency and why you should care about it
jellyfin.org
3M Diskette Reference Manual (1983) [pdf]
retrocmp.de
Beginner-friendly, unofficial documentation for Helix text editor
helix-editor.vercel.app
From 400 Mbps to 1.7 Gbps: A WiFi 7 Debugging Journey
blog.tymscar.com
When reading this project's wiki [0], it mentions that Kanal (another channel implementation) uses an optimization that "makes [the] async API not cancellation-safe". I wonder if this is the same / related issue to the recent HN thread on "future lock" [1]. I hadn't heard of this cancellation safety issue prior to that other HN thread.
[0]: https://github.com/frostyplanet/crossfire-rs/wiki#kanal [1]: https://news.ycombinator.com/item?id=45774086