Live data from Hacker News

Introduction to Compilers and Language Design (2021)

dthain.github.io

51–58 of 58 posts

Re: Introduction to Compilers and Language Design (2021)

#51
post #2

Love such topics and articles in midst of AI topics/noise.

The best part of the blind AI hatred is you can call literally anything AI slop without presenting evidence and the anti-slop loyalists will hate it without any evidence. I do value both correct high quality AI usage and non-AI works, would be nice if we could have a bar for the AI stuff that makes sense instead of dismissing peoples work blindly.

Who said I hated AI ? I just hate the noise.

Have you delegated the self-thinking process to agents as well ?

Re: Introduction to Compilers and Language Design (2021)

#52
This was a great read for me. I'm working on a DSL compiler for 3D printing (after my semester class on compilers) and it's a good reminder of how much there is to learn. It's given me great material on error handling suggestions and constant folding (although mine is not at such an advanced level). I read Chapter 12 on optimization, and it's given me a lot of good ideas in terms of tree rewriting and reducing instruction count. I implemented paging (after much research) but I still deal with crashes partly because the output is still built as a giant string in memory for smaller outputs, and partly because the paging threshold sometimes doesn't trigger early enough. Perhaps there are deeper things for me to optimize and research on. I'm keeping this read under my belt!

Re: Introduction to Compilers and Language Design (2021)

#53

Earlier quoted context omitted.

What's the "tiger book?"

https://www.cambridge.org/core/books/modern-compiler-impleme... Also versions in C and Java.

It really should be read in the SML/NJ as God Intended.

https://www.cs.princeton.edu/~appel/modern/ml/whichver.html

https://www.smlnj.org/

Re: Introduction to Compilers and Language Design (2021)

#54
I really enjoyed Crafting Interpreters by Robert Nystrom and found it valuable for the development of a DSL I'm working on.

From https://craftinginterpreters.com/:

> Crafting Interpreters contains everything you need to implement a full-featured, efficient scripting language. You’ll learn both high-level concepts around parsing and semantics and gritty details like bytecode representation and garbage collection. Your brain will light up with new ideas, and your hands will get dirty and calloused. It’s a blast.

The book is available for free on the website: https://craftinginterpreters.com/contents.html

Re: Introduction to Compilers and Language Design (2021)

#55

Earlier quoted context omitted.

I guarantee half the folk commenting “ai slop” on people’s projects are folk who never read people’s code even before AI. Now they get to dismiss it without providing any specifics and feel superior.

> I guarantee How do you guarantee it, exactly? AI told you in an authoritative tone?

[deleted]

Re: Introduction to Compilers and Language Design (2021)

#56

Earlier quoted context omitted.

I guarantee half the folk commenting “ai slop” on people’s projects are folk who never read people’s code even before AI. Now they get to dismiss it without providing any specifics and feel superior.

> I guarantee How do you guarantee it, exactly? AI told you in an authoritative tone?

I don't actually guarantee it, that would be ridiculous.

Re: Introduction to Compilers and Language Design (2021)

#57
post #50

Earlier quoted context omitted.

I've been working full time for like 3 yrs as C# dev + doing higher edu at weekends at the same time and I was about to decide thesis topic. I've been searching for something challenging and found some very random post on programming forums about how compilers are hard etc and decided to give it a try. I had kind of advantage that I accidentally had some significant amount of experience with handwritten parsers (at f…

Very cool story. I'm interested to do a similar transition, though I was thinking it would be mecessary to go back and do a masters. It's interesting that that might not be required

>though I was thinking it would be mecessary to go back and do a masters. It's interesting that that might not be required

Well, there are no universal rules

Sometimes it could make your life easier, sometimes it wouldnt change anything.

It's kinda luck dependent - what companies you apply for, what hiring manager needs at particular moment, etc.

But if your masters program is same length as mine (1.5 year) then if you feel like doing it, then I recommend it because 1.5 year will pass quickly and you'll have decent paper (and hopefully experience, knowledge, skills and networking) :p

Post reply on HN