this post was submitted on 29 Oct 2023
30 points (100.0% liked)

SneerClub

968 readers
3 users here now

Hurling ordure at the TREACLES, especially those closely related to LessWrong.

AI-Industrial-Complex grift is fine as long as it sufficiently relates to the AI doom from the TREACLES. (Though TechTakes may be more suitable.)

This is sneer club, not debate club. Unless it's amusing debate.

[Especially don't debate the race scientists, if any sneak in - we ban and delete them as unsuitable for the server.]

founded 1 year ago
MODERATORS
 

In today's episode, Yud tries to predict the future of computer science.

you are viewing a single comment's thread
view the rest of the comments
[–] corbin@awful.systems 17 points 10 months ago (24 children)

Yud tried to describe a compiler, but ended up with a tulpa. I wonder why that keeps happening~

Yud would be horrified to learn about INTERCAL (WP, Esolangs), which has required syntax for politely asking the compiler to accept input. The compiler is expressly permitted to refuse inputs for being impolite or excessively polite.

I will not blame anybody for giving up on reading this wall of text. I had to try maybe four or five times, fighting the cringe. Most unrealistic part is having the TA know any better than the student. Yud is completely lacking in the light-hearted brevity that makes this sort of Broccoli Man & Panda Woman rant bearable.

I can somewhat sympathize, in the sense that there are currently multiple frameworks where Python code is intermixed with magic comments which are replaced with more code by ChatGPT during a compilation step. However, this is clearly a party trick which lacks the sheer reproducibility and predictability required for programming.

Y'know, I'll take his implicit wager. I bet that, in 2027, the typical CS student will still be taught with languages whose reference implementations use either:

  1. the classic 1970s-style workflow of parsing, tree transformation, and instruction selection; or
  2. the classic 1980s-style workflow of parsing, bytecode generation, and JIT.
load more comments (23 replies)