Top all-time · #7743
eCorax
Personal blog · ecorax.netprogrammingsystemssecurity
eCorax is a personal blog at ecorax.net about programming, systems and security. Since 2020, 10 different Hacker News readers have linked it 12 times, most often “Tightness Driven Development in Rust”. The last post was in 2021, but the archive is still widely read.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN commenters link eCorax posts on Rust's safety model and unsafe code, GPIO access safety in embedded Rust, and the idea of "type tightness" as an alternative to mocking.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Firmware, fiction, security.
Most-linked posts?
- Tightness Driven Development in Rust3 people · 3 mentions · first linked 2021-05-30
- The GPIO war (Low level GPIO drivers in Rust)3 people · 3 mentions · first linked 2021-03-22
- As above, so below, part 2. Bare metal Rust generics2 people · 2 mentions · first linked 2020-08-31
- Bare Metal Rust Generics2 people · 2 mentions · first linked 2020-08-23
What Hacker News says?
It's moving the goal posts and changing the point of the discussion. We can equally well say that that "Rust formally verifies your safe functions", and that this reduces how much code review is required... it's a matter of degree and specifics. Focusing on pointer manipulations is also misleading: it's entirely true that it's dangerous, but most Rust code does not need to do any sort of raw pointer manipulation. Fo…
Comment linking /as-above-so-below-2/
on “Supporting Linux kernel development in Rust”Submitted Bare Metal Rust Generics as a story · 207 points
HN discussionunsafe isn't like a taint, where things that use unsafe code must propagate their unsafety outward. It's more like saying "there are invariants that this function expects, but does not enforce, and the caller may violate those invariants". Obviously, we want to minimize code like that. The best way to do that is to build abstractions around the unsafe code that only interact with the unsafe code in a way that respec…
Comment linking /macro-bunker-1/
on “Linus Torvalds on where Rust will fit into Linux”Submitted As above, so below, part 2. Bare metal Rust generics as a story · 81 points
HN discussionJust read this. https://www.ecorax.net/as-above-so-below-1/
Comment linking /as-above-so-below-1/
on “Best aspects of C”Submitted Tightness Driven Development in Rust as a story · 6 points
HN discussionI like rust, but don't use it for embedded. Here's a blog I read on how to make GPIO access safe https://www.ecorax.net/macro-bunker-2/ . In that article, they have three goals: verify that the pin is correctly configured, use atomic reads and writes, make sure only one thread (including interrupts) can write to a pin at a time. Spoiler alert, the way they avoid interrupts screwing everything up is with `cortex_m::i…
Comment linking /macro-bunker-2/
on “Is Rust Used Safely by Software Developers?”Submitted The GPIO war (Low level GPIO drivers in Rust) as a story · 6 points
HN discussionI have always liked this approach and, recently, I came across a term for it: "type tightness"[0]. I gotta say, it really stuck with me. [0]: https://www.ecorax.net/tightness/
Comment linking /tightness/
on “I Mock Your Mocks”Submitted Tightness Driven Development in Rust as a story · 3 points
HN discussionSubmitted The GPIO war: macro bunkers for typestate explosions as a story · 3 points
HN discussion
