Top all-time · #1200
Corrode Rust Consulting
Company blog · corrode.dev/blogprogramming
Corrode Rust Consulting is the company blog at corrode.dev, writing about programming. Since 2023, 57 different Hacker News readers have linked it 74 times, most often “The State of Async Rust”. It is still writing: the last post was on 2026-11-02, and you can follow it by feed.
corrode is a friendly Rust consulting company based in Düsseldorf, Germany. We help you build reliable software and ship it to production. We offer consulting, training, and development services for Rust projects. Provided by Matthias Endler.
Most-linked posts?
- The State of Async Rust5 people · 5 mentions · first linked 2023-09-13
- Tips for Faster Rust Compile Times4 people · 4 mentions · first linked 2024-05-15
- Bugs Rust Won't Catch4 people · 4 mentions · first linked 2026-04-29
- Flattening Rust’s learning curve4 people · 4 mentions · first linked 2025-05-05
- Be Simple3 people · 4 mentions · first linked 2025-09-15
- Prototyping in Rust3 people · 3 mentions · first linked 2025-01-17
- Rust is a language for building foundational software3 people · 3 mentions · first linked 2025-06-06
- Thinking in Expressions3 people · 3 mentions · first linked 2025-01-21
- Pitfalls of Safe Rust3 people · 3 mentions · first linked 2025-04-01
- Patterns for Defensive Programming in Rust2 people · 2 mentions · first linked 2025-11-02
What Hacker News says?
Exactly. I wrote an entire blog post about that: https://corrode.dev/blog/dont-use-preludes-and-globs/
Comment linking /blog/dont-use-preludes-and-globs/
on “Greppability is an underrated code metric”Submitted Flattening Rust’s learning curve as a story · 460 points
HN discussionHere are some CVEs identified in Rust coreutils [1]. These are mostly really trivial issues. I'd bet money that the nastier logic bugs are still in there and that the people who maintained the old C utils or helped identify the old bugs can find similar ones in these utils, although half these issues probably never appeared in the C version because Rust is much more complicated than C so makes it easier to hide logi…
Comment linking /blog/bugs-rust-wont-catch/
on “TCP Use-After-Free: CVE-2026-98432 / CVSS 9.8”Submitted Patterns for Defensive Programming in Rust as a story · 333 points
HN discussionDo you mean `Arc<Mutex<T>>`? Yeah, I agree. Wrote a blog post on that topic as well: https://corrode.dev/blog/prototyping/ The title is a bit of a misnomer, but it's about beginner-friendly escape hatches in the language. Perhaps it's useful to newcomers.
Comment linking /blog/prototyping/
on “Flattening Rust’s learning curve”Submitted Pitfalls of Safe Rust as a story · 168 points
HN discussionI spoke with Folkert, one of the developers on this project, on the 'Rust in Production' podcast. Some of you might find it interesting: https://corrode.dev/podcast/s01e05-tweede-golf/
Comment linking /podcast/s01e05-tweede-golf/
on “More Memory Safety for Let's Encrypt: Deploying ntpd-rs”Submitted Don't unwrap options: There are better ways (2024) as a story · 100 points
HN discussionNeither. They basically see Rust as the future. They want to be able to attract young contributors and to hire young employees who are excited about Rust and who want the safety features. Bear in mind, the average age of the Linux developer is increasing. They also see technical benefits in Rust. And they are increasing test coverage of both the Rust tools and the tools written in C, IIRC. My source is this intervie…
Comment linking /podcast/s05e05-canonical/
on “Ubuntu 26.10 completes transition to Rust-based coreutils”Submitted Prototyping in Rust as a story · 30 points
HN discussionInteresting, M1 Max took 6 minutes and M1 Air took 11 minutes according to this article: https://corrode.dev/blog/tips-for-faster-rust-compile-times/...
Comment linking /blog/tips-for-faster-rust-compile-times/
on “Why is the Rust compiler so slow?”Submitted Patterns for Defensive Programming in Rust as a story · 20 points
HN discussionHow many of those advanced concept in Rust such as borrow checker & lifetime could be avoided as a beginner? If utmost performance is not required (i.e., for mortals dealing with Java/Python/JS on a daily basis) would those lifetime and borrow checker concepts be a hinder to move quick? I read this article https://corrode.dev/blog/prototyping/ and it seems to address almost all of my concerns when I started learning…
Comment linking /blog/prototyping/
on “Visualize Ownership and Lifetimes in Rust”Submitted Pitfalls of Safe Rust as a story · 19 points
HN discussionHmm. There are "plenty" of Rust jobs outside of crypto stuff. They are: - Your typical service driven stuff (aka full-stack/backend/microservice et. al) - Tons and tons of opensource projects from AWS (investing), Microsoft (investing) and Google (yes, investing) to name a few off the top of my head. - Startups have so to speak started embracing Rust https://corrode.dev/podcast/ - Embedded Systems <- C/C++/ASM's bre…
Comment linking /podcast/
on “Ask HN: Why am I suddenly unemployable?”Submitted Rust is a language for building foundational software as a story · 12 points
HN discussion> Build times > I'm surprised I didn't see any advice about skipping proc macros or Serde for faster compile times. A more comprehensive document on build times is at https://corrode.dev/blog/tips-for-faster-rust-compile-times/ We're integrating parts of it into Cargo's official documentation at https://doc.rust-lang.org/nightly/cargo/guide/build-performa... We're coordinating the work on that at https://github.com/…
Comment linking /blog/tips-for-faster-rust-compile-times/
on “The Rust Performance Book (2020)”Submitted Rust in Production: Volvo Ships Memory-Safe ECUs in Production Cars as a story · 12 points
HN discussionAuthor here; thanks! I had the same impression, which is why I started writing these short-form articles about idiomatic Rust. The blog post overview is here: https://corrode.dev/blog/
Comment linking /blog/
on “Don't unwrap options: There are better ways (2024)”Submitted Tips for Faster Rust Compile Times as a story · 6 points
HN discussionLanguage hype always justifies itself through intellectualizing its own desire. In this incarnation we don't always hear, "Rust is the future."[1] We hear: * "improving security, ensuring long-term maintainability, and optimizing performance" "memory safety, concurrency, and performance" [2] * "its ability to prevent common programming errors such as null pointer dereferences and buffer overflows" [3] * "is that it'…
Comment linking /blog/foundational-software/
on “The allure of new languages vs. the necessity of problem-solving”Submitted We Have Named Arguments at Home as a story · 5 points
HN discussion44 CVE's : https://corrode.dev/blog/bugs-rust-wont-catch/ Also stuff like: "Set Permissions at Creation Time, Not After"
Comment linking /blog/bugs-rust-wont-catch/
on “OpenBSD Developers Reject Uutils Coreutils”Submitted Tips for Faster Rust Compile Times as a story · 4 points
HN discussionI’m not aware of any memory corruption bugs, but some weird cases where Linux, stuck with legacy 8-bit character handling for filenames and paths, lead to unesirable behavior with Rust’s native Unicode strings. The race conditions were indeed TOCTOU bugs. In a sense, the bugs were a result of incorrectly handling shared mutable data, though in this case the mutations were external to Rust. https://corrode.dev/blog/b…
Comment linking /blog/bugs-rust-wont-catch/
on “Maybe you shouldn't install new software for a bit”Submitted Be Simple as a story · 4 points
HN discussionIt's a mixed bag of a blog post. Reading it, and your response, I see all of this as growing pains. The Rust async split mentioned in the post is a legitimate issue. It's also a consequence of immaturity. Rust async underspecified async runtimes and, naturally, incompatible async runtimes emerged and leak all over. The shrapnel of that plagues crates.io. A thoughtful post about this is found here[1]. On the other ha…
Comment linking /blog/async/
on “Async Rust Isn't Bad: You Are”Submitted Be Simple as a story · 4 points
HN discussionThe article seems to be just a way to say "Rust is better" - and it fails to do so by spreading misinformation such as the channels part ( https://corrode.dev/learn/migration-guides/go-to-rust/#chann... ) or making a fair comparison of pprof vs Rust's flamegraph. It also skips entirely over debugging (delve vs gdb), IDE support, ecosystem (why the hell does Rust have N async runtimes?!), statically linking and so on…
Comment linking /learn/migration-guides/go-to-rust/
on “Migrating from Go to Rust”Submitted Flattening Rust's Learning Curve as a story · 4 points
HN discussion
