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

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

betlang.dev

Post reply on HN
Print view View original

21–30 of 38 posts

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

#21

Post by dmurvihill »

senbrow wrote: post #18
vofx wrote: 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 s…

Actually, the group in question have repeatedly and vocally asked others to speak up when they see nonsense like this.

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

#22

Post by Tallain »

andai wrote: 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…

Thanks! I hate it!

In awe at whatever inspired this though

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

#23

Post by kmoser »

andai wrote: 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 this in 1989, as if C had been written by the folks who brought you COBOL:

  #include 

  #define OpenBrace {
  #define CloseBrace }
  #define OpenBracket [
  #define CloseBracket ]
  #define OpenParenthesis (
  #define CloseParenthesis )
  #define NoReturnType void
  #define NoParameter NoReturnType
  #define MainFunction main
  #define Semicolon ;
  #define FunctionPrototype
  #define ActualFunction
  #define PointerTo(atype) atype*
  #define OutputToStdout(astring) printf(astring)
  #define IsEqualTo =

  FunctionPrototype NoReturnType
  MainFunction OpenParenthesis NoParameter CloseParenthesis Semicolon

  ActualFunction NoReturnType
  MainFunction OpenParenthesis NoParameter CloseParenthesis
  OpenBrace
    PointerTo(char) string IsEqualTo "Now is the time for all good men, etc.\n" Semicolon
    OutputToStdout(string) Semicolon
  CloseBrace

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

#24

Post by giancarlostoro »

andai wrote: 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…

Reminds me of my "BASIC" #define statements I made in college to make C look slightly more BASIC-like, I think everyone does this the moment they realize they can do this in C.

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

#25

Post by ahmadyan »

Nicely done Geoffrey, I think we are coming full circle, instead of porting projects to different languages (for whatever) like going from zig -> rust -> zig, now we can also add additional hops like zig -> rust -> curse -> ts -> ocaml -> english -> zig.

Thank you for keeping the token furnace burning!

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

#26

Post by bitwize »

kmoser wrote: post #23
andai wrote: 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 this in 1989, as if C had been written by the folks who brought you COBOL: #include #define OpenBrace { #define CloseBrace } #define OpenBracket [ #define CloseBracket ] #define OpenParenthesis ( #define CloseParenthesis ) #define NoReturnType void #define NoParameter NoReturnType #define MainFunction main #define Semicolon ; #define FunctionPrototype #define ActualFunction #define PointerTo(atype) atype* #defi…

Needs more DIVISIONs. Though I can imagine this being what would happen if the designers of PowerShell were responsible for C.

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

#27

Post by onlyrealcuzzo »

jdw64 wrote: post #12
swiftcoder wrote: post #9

Earlier quoted context omitted.

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.

Well... The fact that it took 10x longer for Doom to build than the language tells a lot.

Doom is not harder to re-implement than a language.

The language does not "work" by any sense of the word - which is why it took Doom so long to implement.

You could get GPT to "self host" a "language" in 5 hrs. That's not impressive.

The language actually working and being non-trivial would be in 20x the time.

Sure, GPT can build yet-another-Lisp in 2 minutes. You could copy Lispy yourself in that time: https://www.norvig.com/lispy.html

GPT/Fable/what have you is not building this language, as its laid out, and "working" in a true sense that fast.

Either OP is completely full of it, the language didn't actually work (and likely still doesn't), or the language is far less sophisticated than it seems from the examples - it's and the examples are minimal, so it's kind of hard to tell what it actually does...

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

#28

Post by bitwize »

giancarlostoro wrote: post #24
andai wrote: 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…

Reminds me of my "BASIC" #define statements I made in college to make C look slightly more BASIC-like, I think everyone does this the moment they realize they can do this in C.

Stephen Bourne was a fan of Algol 68, and the original Bourne shell was written in "Bournegol", which is C with enough #define malarkey to make it more Algol-like:

https://www.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd/sh...

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

#29

Post by jrapdx3 »

bitwize wrote: post #26
kmoser wrote: post #23

Earlier quoted context omitted.

I did this in 1989, as if C had been written by the folks who brought you COBOL: #include #define OpenBrace { #define CloseBrace } #define OpenBracket [ #define CloseBracket ] #define OpenParenthesis ( #define CloseParenthesis ) #define NoReturnType void #define NoParameter NoReturnType #define MainFunction main #define Semicolon ; #define FunctionPrototype #define ActualFunction #define PointerTo(atype) atype* #defi…

Needs more DIVISIONs. Though I can imagine this being what would happen if the designers of PowerShell were responsible for C.

How right you are! I use PowerShell when I have to.

Seems like PS was designed under the motto, "The choice: why make it simple when we can make it complicated?"

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

#30

Post by anthk »

bitwize wrote: post #28
giancarlostoro wrote: post #24

Earlier quoted context omitted.

Reminds me of my "BASIC" #define statements I made in college to make C look slightly more BASIC-like, I think everyone does this the moment they realize they can do this in C.

Stephen Bourne was a fan of Algol 68, and the original Bourne shell was written in "Bournegol", which is C with enough #define malarkey to make it more Algol-like: https://www.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd/sh...

I was about to post this.
Post reply on HN