Top all-time · #6433
Rui Ueyama
Personal blog · sigbus.infoprogrammingsystems
Rui Ueyama's personal blog at sigbus.info covers programming and systems. Since 2015, 12 different Hacker News readers have linked it 16 times, most often “I wrote a self-hosting C compiler in 40 days (2015)”. No feed was found, so read it on the site itself.
Too few sampled comments (9) to say how often HN recommends it.?
Why HN links it
Commenters link this blog for posts on writing C compilers, such as the 8cc and self-hosting C compiler diaries and a Japanese compiler book. Some also cite an essay on 'worse is better'. None praise it directly.
Summarised by Claude from a sample of 9 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- I wrote a self-hosting C compiler in 40 days (2015)4 people · 4 mentions · first linked 2019-09-05
- How I wrote a self-hosting C compiler in 40 days3 people · 3 mentions · first linked 2015-12-14
- Software compatibility and our own “User-Agent” problem3 people · 3 mentions · first linked 2017-12-11
- /compilerbook2 people · 2 mentions · first linked 2019-09-05
- My story on “worse is better” (2018)2 people · 2 mentions · first linked 2022-05-11
What Hacker News says?
Here is an example of the "good bot"/"bad bot" nonsense in action. This is an article about the LinkedIn v hiQ case at AdWeek. curl --user-agent INSERT_ANYTHING_HERE http://www.adweek.com/digital/rami-essaid-distil-networks-guest-post-linkedin-hiq-labs/ It seems AdWeek can distinguish a "good bot" from a "bad bot" irrespective of the behavior of the user^W bot, i.e., whether it is one single HTTP request or 10,000 c…
Comment linking /software-compatibility-and-our-own-user-agent-problem.html
on “Accessing Publicly Available Information on the Internet Is Not a Crime”Submitted How I wrote a self-hosting C compiler in 40 days as a story · 429 points
HN discussionFirst place I read about this idea (specifically newlines, not in general trusting trust) was day 42 in https://www.sigbus.info/how-i-wrote-a-self-hosting-c-compile... "For example, my compiler interprets "\n" (a sequence of backslash and character "n") in a string literal as "\n" (a newline character in this case). If you think about this, you would find this a little bit weird, because it does not have information…
Comment linking /how-i-wrote-a-self-hosting-c-compiler-in-40-days
on “Whence '\n'?”Submitted I wrote a self-hosting C compiler in 40 days (2015) as a story · 259 points
HN discussionAuthor here. No publishing date has been set yet. At least a half-written Japanese version of the book is available online for free ( https://www.sigbus.info/compilerbook ), and I'll probably translate this to English and share at least a few chapters for free. But nothing is set in stone yet. There's no mailing list for notifications yet.
Comment linking /compilerbook
on “Chibicc: A Small C Compiler”Submitted My story on “worse is better” (2018) as a story · 195 points
HN discussionYou could write to the author or follow their social media: https://www.sigbus.info/
Comment linking /
on “Chibicc: A Small C Compiler”Submitted Software compatibility and our own “User-Agent” problem as a story · 194 points
HN discussionThe author has since written a longer book on how to write compilers (albeit in Japanese): https://www.sigbus.info/compilerbook
Comment linking /compilerbook
on “I wrote a self-hosting C compiler in 40 days (2015)”Submitted I wrote a self-hosting C compiler in 40 days (2015) as a story · 116 points
HN discussionIn my experience, a new toy c compiler pops up roughly once a year. https://github.com/Wilfred/babyc http://www.sigbus.info/how-i-wrote-a-self-hosting-c-compiler... http://zserge.com/blog/cucu-part1.html https://c9x.me/qcc/ https://github.com/alexfru/SmallerC
Comment linking /how-i-wrote-a-self-hosting-c-compiler-in-40-days.html
on “Integrating “safe” languages into OpenBSD?”Submitted LLVM/lld linker and its "User-Agent" compatibility problem as a story · 7 points
HN discussion"a version that outputs AMD64 assembly" It's not based on the linked guide, but there's 8cc. Outputs x86-64 only. Diary of it being made: https://www.sigbus.info/how-i-wrote-a-self-hosting-c-compile... Github sources and history: https://github.com/rui314/8cc The "gen.c" source file might be helpful for some of your questions about x86-64: https://github.com/rui314/8cc/blob/b8a46abdb5f0633bdbff31482...
Comment linking /how-i-wrote-a-self-hosting-c-compiler-in-40-days
on “Let’s Build a Compiler (1995)”Submitted Software compatibility and lld linker’s “User-Agent” problem as a story · 2 points
HN discussionHere's my take[1] on it. In essence, # Learning Resources ## Theory Take a look at these two books: - Crafting Interpreters[2]. Compilers and interpreters have a lot in common and the book is exceptionally beginner-friendly. Basically, this is the perfect one to get started with. - Introduction to Compilers and Language Design[3]. Doesn’t assume any preexisting compilers knowledge, and teaches all the basics necessa…
Comment linking /how-i-wrote-a-self-hosting-c-compiler-in-40-days
on “Apple hiring compiler developers for improving Swift / C++ interoperability”Centralization is the #1 solution. It works. It's "ugly", but it works. You see even on this thread people begging for one single standard. What actually happens with that one single standard? - Behind it, you have a shittload of people implicitly optimizing for the general use case and hiding all the said complexity for you - No need to worry about [semantic conflict]( https://www.sigbus.info/worse-is-better ) Once…
Comment linking /worse-is-better
on “Composition Shouldn't be this Hard”
