Languages
Post #7074 · source on Telegram
Therapist Asks Rust Developer If Zero-Cost Abstractions Are In the Room
Description
A meme with the text 'So are those "zero-cost abstractions" in the room with us right now?' above a still from a psychiatric evaluation scene showing a doctor/therapist sitting across a table from a patient in a hospital gown. The image references the therapy session meme format where the therapist implies the patient is imagining things. The joke targets Rust programming language's promise of 'zero-cost abstractions' -- a core selling point that abstraction layers compile away with no runtime overhead -- suggesting that in practice, the abstractions may not be as zero-cost as advertised, or that Rust developers are delusional about their language's promises
More like this
More like this in Languages →
Use J and K for navigation
Comments
9Comment deleted
The zero-cost abstractions are very real, doctor -- they just moved all their cost to compile time, developer sanity, and 47 lifetime annotations
Zero-cost abstractions are like free lunches at scale - great until the profiler itemizes dessert
After 20 years of being promised zero-cost abstractions, we've learned they're like microservices with zero latency - theoretically possible if you ignore physics, cache misses, and the fact that your compiler isn't actually magic
The therapist gently asks about zero-cost abstractions while the patient insists they're real, completely unaware that the session itself is being billed at $300/hour - a perfect metaphor for how 'zero-cost' often just means 'someone else pays the price.' In reality, those abstractions cost you in compile times, binary size, and the cognitive overhead of explaining to your team why the build now takes 45 minutes. But hey, at least the runtime is fast... assuming you can afford the CI/CD bills
Zero‑cost is a great alibi - until perf shows a vtable hop, cross‑crate LTO was off, and your hot path confesses via i‑cache misses
Zero-cost abstractions: zero runtime overhead, but your monomorphized binaries beg to differ on disk space
They’re only “zero‑cost” once -O3+LTO, devirtualization, and monomorphization remove the cuffs; otherwise your profiler knows exactly where they’re sitting
no, they've got compiled away Comment deleted
Zero-cost in runtime, but not in comptime Comment deleted