Remix.run Logo
zby an hour ago

What do you do to learn new programming construct? What did you do to learn programming - didn't you write

  #include <stdio.h>

  int main() {

    printf("Hello World");
    return 0;
  }
while having no idea what 'stdio.h' is?
bitwize 20 minutes ago | parent | next [-]

Funny you should mention hello world. Kernighan and Ritchie presented it in TCPL as a little anatomical diagram of close to the smallest possible functional C program with the different parts labelled. The first line is labelled "include information about the standard library". What this means in detail is explained in that chapter. Furthermore, if you were compiling on a Unix system, stdio.h was readily available as /usr/include/stdio.h. Curious people could open it up using more or vi and see what was inside. There was no shortage of curious people back then.

The process of "going through the motions" of writing and compiling a program without even a small understanding of what it all meant was a later innovation, perhaps done as a classroom exercise in an introductory CS course for impatient freshmen or similar.

irishcoffee an hour ago | parent | prev | next [-]

Choosing not to know what stdio.h means is willful ignorance, an LLM has little to do with said chosen ignorance, that is a choice because "hey it works on machine!" and when I pushed it, nobody seemed to mind.

What a time to be alive. Actively choosing to rebuke knowledge because "what the fuck does it matter anyways"

nice_byte an hour ago | parent | prev [-]

no. it was the first question I asked and was given a satisfactory explanation (along the lines of, "this adds things to your program that help it write text to the screen.")

Almondsetat an hour ago | parent [-]

That's not even remotely satisfactory if we're talking about understanding what we're doing