Top all-time · #9921
Coding in Old Entish
Personal blog · chandlerc.blogprogrammingsystems
Coding in Old Entish is a personal blog at chandlerc.blog about programming and systems. Since 2023, 8 different Hacker News readers have linked it 11 times, most often “Story-time: C++, bounds checking, performance, and compilers”. It is still writing: the last post was on 2024-11-16, and you can follow it by feed.
Too few sampled comments (3) to say how often HN recommends it.?
Why HN links it
HN commenters cite the author's Carbon strategy slides and talk on C++ memory safety and borrow checking. The comments only reference these materials as sources for their own points.
Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Chandler's blog about programming, languages, compilers, performance, cpus, tech, and everything else.
Most-linked posts?
- Story-time: C++, bounds checking, performance, and compilers6 people · 6 mentions · first linked 2024-11-17
What Hacker News says?
>Carbon wants to ship a finished working Carbon language, then bolt on safety (somehow) but, only for some things, not data races for example, so, you still don't actually have Rust's Memory Safety I'm not sure this is correct. As I understand it, Carbon's plan is to add a borrow checker like Rust's. From a recent talk[0][1] by one of the lead developers: >Best candidate for C++ is likely similar to Rust’s borrow ch…
Comment linking /slides/2023-cppnow-carbon-strategy/index.html
on “Circle C++ with memory safety”Submitted Story-time: C++, bounds checking, performance, and compilers as a story · 7 points
HN discussionA really good accompaniment to this is Carruth's "C++, bounds checking, performance, and compilers" [1]: > ... strong belief that bounds checks couldn’t realistically be made cheap enough to enable by default. However, so far they are looking very affordable. From the above post, 0.3% for bounds checks in all the standard library types! There's more to the hardening story than just bounds checks. But it's a big part…
Comment linking /posts/2024/11/story-time-bounds-checking/
on “Hardening mode for the compiler”Submitted Story-time: C++, bounds checking, performance, and compilers as a story · 5 points
HN discussionUnless something has chnaged since this talk[0][1], I don't think that is accurate. >Best candidate for C++ is likely similar to Rust’s borrow checker It is stated clearly in the talk that this is true for Carbon as well [0] https://chandlerc.blog/slides/2023-cppnow-carbon-strategy/in... [1] relevant timestamps: https://youtube.com/watch?v=1ZTJ9omXOQ0&t=1h31m34s https://youtube.com/watch?v=1ZTJ9omXOQ0&t=1h9m49s
Comment linking /slides/2023-cppnow-carbon-strategy/index.html
on “Secure by Design: Google's Perspective on Memory Safety”Submitted Story-time: C++, bounds checking, performance, and compilers as a story · 4 points
HN discussionSubmitted Story-time: C++, bounds checking, performance, and compilers as a story · 3 points
HN discussionSubmitted C++, bounds checking, performance, and compilers as a story · 3 points
HN discussionSubmitted Carbon Language: Road to 0.1 as a story · 3 points
HN discussionSubmitted Carbon memory safety: a first deep dive as a story · 1 points
HN discussionSubmitted The little things in programming languages #1: Access control as a story · 1 points
HN discussion
