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

Doom, Played over Curl

github.com

Post reply on HN
Print view View original

21–30 of 36 posts

Re: Doom, Played over Curl

#21

Post by moeffju »

z3c0 wrote: post #11
varun_ch wrote: post #6

One interesting side effect of having a LLM write the thing including the README, is that the models tend to leave little hints of the authors intention or prompt as over-explained passages that make it obvious that AI help was used. https://github.com/xsawyerx/curl-doom?tab=readme-ov-file#how... eg. > A browser hitting the same URL gets a tiny landing page that just shows the one-liner it’s subtle but once you notic…

Not to mention that the objectively bad practice of piping a curl call to bash is nowhere close to "playing doom via curl". It's almost as if they simply prompted "play doom with curl". In my experience, almost any overly-ambitious prompt ends similarly.

But that's not what it does, the bash option just saves you from doing stty setup and reset I think? You can just type it all out by hand, too, as the readme explains

Re: Doom, Played over Curl

#22

Post by moeffju »

Leomuck wrote: post #8

What the hell. First, I thought this was crazy. How could you do anything crazy with curl? But of course, curling a bash script opens lots of opportunities. Given the right permissions, you could run an enterprise Jira server via only a curl to a bash script. Still cool that people find more ways to play doom, but calling it "via curl" seems a little missleading to me. "Playing doom via a simple bash script" would ha…

Isn't it literally playing it via curl though - curl reads STDIN and transmits that to the server, which responds. The whole bash thing is completely optional and only saves you some tty setup.

Re: Doom, Played over Curl

#24

Post by reactordev »

nurettin wrote: post #13
reactordev wrote: post #9

oddly enough, this is how it looked when I ran it on my 486 when I was a kid. Pretty accurate except this runs at a faster fps than mine did... ;)

I remember Liquid crystal displays having an unintended blur effect when something animates or rotates, but it wasn't as bad as ansi chars.

rofl, my AGP VGA CRT had permanent ghosting damage from the Doom logo. So yeah, I feel this.

Re: Doom, Played over Curl

#25

Post by BobbyTables2 »

I’m shocked that curl is fancy enough to start reading and outputting the HTTP response before the request has even been fully sent!

I wasn’t expecting that a “simple” command line application supports this kind of thing — the HTTP spec is crazy enough that I can’t say I’m surprised it’s not forbidden.

Re: Doom, Played over Curl

#26

Post by z3c0 »

moeffju wrote: post #21
z3c0 wrote: post #11

Earlier quoted context omitted.

Not to mention that the objectively bad practice of piping a curl call to bash is nowhere close to "playing doom via curl". It's almost as if they simply prompted "play doom with curl". In my experience, almost any overly-ambitious prompt ends similarly.

But that's not what it does, the bash option just saves you from doing stty setup and reset I think? You can just type it all out by hand, too, as the readme explains

You know what, I stand corrected. I missed this portion of play.sh: https://github.com/xsawyerx/curl-doom/blob/ae1edb82e48efcd2d...

I'm not changing where I stand on piping to bash.

Re: Doom, Played over Curl

#29

Post by xsawyerx »

varun_ch wrote: post #6

One interesting side effect of having a LLM write the thing including the README, is that the models tend to leave little hints of the authors intention or prompt as over-explained passages that make it obvious that AI help was used. https://github.com/xsawyerx/curl-doom?tab=readme-ov-file#how... eg. > A browser hitting the same URL gets a tiny landing page that just shows the one-liner it’s subtle but once you notic…

I think you're assuming a lot on how LLM was used here. I understand why you would, but it doesn't make it correct. You found me documenting how something works in the style that I do and you assume I just LLM'ed the entire thing.

Like I said, I understand why, but still...

Re: Doom, Played over Curl

#30

Post by xsawyerx »

z3c0 wrote: post #11
varun_ch wrote: post #6

One interesting side effect of having a LLM write the thing including the README, is that the models tend to leave little hints of the authors intention or prompt as over-explained passages that make it obvious that AI help was used. https://github.com/xsawyerx/curl-doom?tab=readme-ov-file#how... eg. > A browser hitting the same URL gets a tiny landing page that just shows the one-liner it’s subtle but once you notic…

Not to mention that the objectively bad practice of piping a curl call to bash is nowhere close to "playing doom via curl". It's almost as if they simply prompted "play doom with curl". In my experience, almost any overly-ambitious prompt ends similarly.

One form is to `curl` to get the bash code to just run the loop on keys that make additional curl requests. That is playing DOOM via curl. Each curl is a movement.

However, if you see the next form, it creates a single curl request that stays open and does not need bash or additional calls for each key. It uses the open request. (You do need to set the terminal to raw for this.)

HOWEVER, to push back against myself: It's relatively easy to do when other people did the heavy lifting: Doomgeneric, terminals, curl, etc. I also couldn't use websockets because it doesn't come with curl by default. And you can also move forward only when pressing a button to refresh the frame.

So yeah, not the most impressive thing by far. But it is curl used to play the game and that's... something?

Post reply on HN