Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introduction to Compilers and Language Design (2021)

dthain.github.io

Post reply on HN
Print view View original

11–20 of 58 posts

Re: Introduction to Compilers and Language Design (2021)

#11

Post by dixtel »

jdw64 wrote: post #7
t-3 wrote: post #6

Earlier quoted context omitted.

Assembly generation is actually pretty simple, it's optimizing everything that's difficult. Writing an assembler is a great way to get acquainted with compiler construction, because you don't need to think about optimization and types and the other features that make high level languages complicated aren't needed.

I keep saying 'someday...' and never actually doing it because of making a living, but this time I think I should try a few small examples

I fell you, My dream is to build my own compiler for WASM to use it later for my own pet projects. But after 9-5 job I'm exhusted and only able to work for max 1 hour.

But I still have hope that I will make it. Maybe coding agent will help me but I dont like the idea that I need help from AI to build this. I want to create compilers through my own hands.

Anyway, I hope you will make it anyway. :)

Re: Introduction to Compilers and Language Design (2021)

#12

Post by [deleted] »

solumunus wrote: post #10
giancarlostoro wrote: post #9

Earlier quoted context omitted.

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.

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.

[deleted]

Re: Introduction to Compilers and Language Design (2021)

#15

Post by Jtsummers »

swordlucky666 wrote: post #4

[flagged]

https://news.ycombinator.com/threads?id=swordlucky666 - Sort of embarrassing that anyone vouched for this comment. Reading their history, they copy/paste the same comment or use an autogenerator (probably not an LLM, that'd produce better results) to generate comments like this one.

Here's a comical one:

https://news.ycombinator.com/item?id=48445529

> The discussion on Spanish traders set the standa raises interesting points. In practical applications, the key challenge is balancing performance with maintainability. Would be valuable to see more concrete examples of trade-offs. [emphasis added]

They glob out part of the submission title (and took too much and cut off in the middle of a word) generating a delightful nonsense descriptor (the italicized bit). The title being:

> Spanish traders set the standard for GnuCash database design

Re: Introduction to Compilers and Language Design (2021)

#16

Post by klez »

Jtsummers wrote: post #15
swordlucky666 wrote: post #4

[flagged]

https://news.ycombinator.com/threads?id=swordlucky666 - Sort of embarrassing that anyone vouched for this comment. Reading their history, they copy/paste the same comment or use an autogenerator (probably not an LLM, that'd produce better results) to generate comments like this one. Here's a comical one: https://news.ycombinator.com/item?id=48445529 > The discussion on Spanish traders set the standa raises interestin…

> Sort of embarrassing that anyone vouched for this comment

I'm the one who vouched it. I don't check commenters' history before doing it. Maybe I should. My LLM-detector is apparently broken (especially on short posts). At face value I saw nothing wrong with it, so I vouched it.

Re: Introduction to Compilers and Language Design (2021)

#17

Post by sethhochberg »

jdw64 wrote: post #3

Sometimes I see people who design languages and build compilers, and I find them truly amazing. I once tried making a language myself because I was curious, but it was so difficult that I just settled for a simple C backend. The people contributing to LLVM probably know everything down to assembly generation. they're truly incredible.

Honestly whipping up a lexer/parser and a REPL is one of my favorite ways to learn a new language. You can cover a lot of ground in a "real" language by just doing the frontend implementation of your own made-up language grammar and a little eval loop and its great for learning/teaching because you don't get bogged down in trying to solve some actual problem.

Which is to say: no shame in just settling for that simple C backend!

Re: Introduction to Compilers and Language Design (2021)

#18

Post by Jtsummers »

klez wrote: post #16
Jtsummers wrote: post #15

Earlier quoted context omitted.

https://news.ycombinator.com/threads?id=swordlucky666 - Sort of embarrassing that anyone vouched for this comment. Reading their history, they copy/paste the same comment or use an autogenerator (probably not an LLM, that'd produce better results) to generate comments like this one. Here's a comical one: https://news.ycombinator.com/item?id=48445529 > The discussion on Spanish traders set the standa raises interestin…

> Sort of embarrassing that anyone vouched for this comment I'm the one who vouched it. I don't check commenters' history before doing it. Maybe I should. My LLM-detector is apparently broken (especially on short posts). At face value I saw nothing wrong with it, so I vouched it.

I often check the history for comments that start off [dead] because I like to see if:

1. There's a problem with the account (and then inform them and maybe notify the mods myself). Sometimes people get shadowbanned without good reason (usually the result of automoderation, not an explicit human moderator action) or for something that happened years ago, but their history is pretty clean since.

2. To see if the person is just a spammer (as is the case here).

Though I only do this if the comment seems like something that oughtn't be dead (as this one does on a first glance). The comment is shallow, but not necessarily wrong or bad. It just adds little to the discussion since it boils down to "The book is an introductory text." which we also get from reading the submission title.

Re: Introduction to Compilers and Language Design (2021)

#19

Post by vidarh »

Jtsummers wrote: post #18
klez wrote: post #16

Earlier quoted context omitted.

> Sort of embarrassing that anyone vouched for this comment I'm the one who vouched it. I don't check commenters' history before doing it. Maybe I should. My LLM-detector is apparently broken (especially on short posts). At face value I saw nothing wrong with it, so I vouched it.

I often check the history for comments that start off [dead] because I like to see if: 1. There's a problem with the account (and then inform them and maybe notify the mods myself). Sometimes people get shadowbanned without good reason (usually the result of automoderation, not an explicit human moderator action) or for something that happened years ago, but their history is pretty clean since. 2. To see if the perso…

Yeah, I take the same approach, and as much as I'm generally very pro AI use, to the point I wouldn't really mind AI comments if they added value (but it's fine it'll remain against the rules here), it really has become necessary to read the comments history before vouching, sadly, given they all seem to be low quality noise.
Post reply on HN