Live data from Hacker News

56,000 lines of DOOM, in a language I made up

betlang.dev

11–20 of 38 posts

Re: 56,000 lines of DOOM, in a language I made up

#11
post #5

Excellent. At last, I can I confess a far worse crime. Late 2020, pre-AI, which I'm not sure if that makes it better or worse... #include "uwu.h" #include iwint main() stawt iwint owo is 5 yiff fuw (iwint uwu is 0 yiff uwu smol owo yiff uwu incwease) stawt owo is owo wif uwu yiff spweak nuwumber_fowmat, owo spwake yiff stawp stawp -- // uwu.h #define is = #define yiff ; #define stawt { #define stawp } #define fuw for…

this gave me such a good chuckle :p

Re: 56,000 lines of DOOM, in a language I made up

#12
post #7

I'm writing the C backend by hand and using AI for the rest, so how did this author manage to finish an entire language in just 34 hours? I've been steadily catching and fixing what the AI writes, so it's amazing to me that they ended up with a complete language. It makes me wonder if the way I'm building a compiler is just wrong.

If you tell it to write a spec -> then write the tests -> then implement, the LLM should be able to pretty much one-shot a compiler frontend. LLMs really benefit from the kind of task that has a built-in validation loop.

I'm working on something similar, but unlike the author, my progress has been pretty slow. It's tough. I do write about a fifth of the code myself, but I keep getting stuck on the rest.

Re: 56,000 lines of DOOM, in a language I made up

#13
post #5

Excellent. At last, I can I confess a far worse crime. Late 2020, pre-AI, which I'm not sure if that makes it better or worse... #include "uwu.h" #include iwint main() stawt iwint owo is 5 yiff fuw (iwint uwu is 0 yiff uwu smol owo yiff uwu incwease) stawt owo is owo wif uwu yiff spweak nuwumber_fowmat, owo spwake yiff stawp stawp -- // uwu.h #define is = #define yiff ; #define stawt { #define stawp } #define fuw for…

I did the same thing, shouting.h, defined the uppercase version of many types and keywords.

Had a good uncontrolled laugh during a team presentation with a colleague. It was a bit disrespectful for the poor presenter who had nothing to do with this…

Can't find shouting.h anymore unfortunately.

Re: 56,000 lines of DOOM, in a language I made up

#16
post #2

This is a good example of where it’s important to be more up front about the role of AI in the making of a thing. Making a language that compiles through LLVM is no small task and takes a lot of expertise. Most of the time people do it because they have a point of view and are highly technical. Making a joke language via AI is an entirely different exercise. Not without value but not the same, especially when evaluat…

I made a “fully” functioning programming language that is kind of like Rebol on luajit using Claude code - and I haven’t really done much serious programming since college 20 years ago. It’s fun though.

Re: 56,000 lines of DOOM, in a language I made up

#17
post #5

Excellent. At last, I can I confess a far worse crime. Late 2020, pre-AI, which I'm not sure if that makes it better or worse... #include "uwu.h" #include iwint main() stawt iwint owo is 5 yiff fuw (iwint uwu is 0 yiff uwu smol owo yiff uwu incwease) stawt owo is owo wif uwu yiff spweak nuwumber_fowmat, owo spwake yiff stawp stawp -- // uwu.h #define is = #define yiff ; #define stawt { #define stawp } #define fuw for…

uwu, this is amazing ;3

Re: 56,000 lines of DOOM, in a language I made up

#18
post #3

[flagged]

I know you probably mean very well, but IMO it's really bizarre and patronizing to be offended on someone else's behalf, especially if the offended people in question are perfectly capable of expressing the sentiment themselves.

If there's actual outrage from the group, it will surface from them without your involvement.

If it offends YOU, just say so plainly.

The hypothetically offended group doesn't need a random stranger to white knight for them in the comment section of a niche tech news website.

Re: 56,000 lines of DOOM, in a language I made up

#19
post #7

I'm writing the C backend by hand and using AI for the rest, so how did this author manage to finish an entire language in just 34 hours? I've been steadily catching and fixing what the AI writes, so it's amazing to me that they ended up with a complete language. It makes me wonder if the way I'm building a compiler is just wrong.

[deleted]

Re: 56,000 lines of DOOM, in a language I made up

#20
post #2

This is a good example of where it’s important to be more up front about the role of AI in the making of a thing. Making a language that compiles through LLVM is no small task and takes a lot of expertise. Most of the time people do it because they have a point of view and are highly technical. Making a joke language via AI is an entirely different exercise. Not without value but not the same, especially when evaluat…

> This is a good example of where it’s important to be more up front about the role of AI in the making of a thing.

Maybe, but we don’t always discuss our tool stack before showing our work because a lot of times it’s assumed or not interesting. AI is a tool, it’s a lever that you push on to multiply your effort. The product of your effort speaks for itself, as it always has.

Post reply on HN