Live data from Hacker News

Dwarf Fortress in the Browser

github.com

1–10 of 29 posts

Re: Dwarf Fortress in the Browser

#4
Honest question. Do people read these massive vibe-coded README.md files, or are they just artifacts?

The minute I see them, I tune out and move on. These types of docs come across to me as so over-specified and memorialized that I just find it not worth the effort to read. Of course for legacy projects this type of documentation would have been invaluable. What's changed, I wonder?

Re: Dwarf Fortress in the Browser

#5
post #4

Honest question. Do people read these massive vibe-coded README.md files, or are they just artifacts? The minute I see them, I tune out and move on. These types of docs come across to me as so over-specified and memorialized that I just find it not worth the effort to read. Of course for legacy projects this type of documentation would have been invaluable. What's changed, I wonder?

We're in an era where the documentation is written to be read by LLM's, and I fully expect the README files to follow suit.

Re: Dwarf Fortress in the Browser

#6

    But... why.... from all possible protocols and options out there for secure, and less complex channels out there... they chose the so featureful and pure overhead as SSH...  

    For low-latency VNC+Audio, why not WireGuard, WebRTC, QUIC etc.?

    Yes, Dungeon Crawl Stone Soup approached it relatively similarly for WebTiles, yet... it's infinitely different magnificent titles...  

    Oh... it's not them... it's Claude they used... or? Who knows, right? No one, including the priceless invaluable ideas of actual developers meat-ground into the Claude datasets now being sold for tokens...  

    // https://i.imgur.com/FM4aTMZ.png - SSH
    // https://i.imgur.com/9lZniqE.png - Claude

Re: Dwarf Fortress in the Browser

#7
post #4

Honest question. Do people read these massive vibe-coded README.md files, or are they just artifacts? The minute I see them, I tune out and move on. These types of docs come across to me as so over-specified and memorialized that I just find it not worth the effort to read. Of course for legacy projects this type of documentation would have been invaluable. What's changed, I wonder?

We're in an era where the documentation is written to be read by LLM's, and I fully expect the README files to follow suit.

Isn't this the whole point of an AGENTS.md file? So that you can leave the readme for humans and put LLM-friendly crap in a separate file?

Re: Dwarf Fortress in the Browser

#8
Sooo it’s just streaming a game to your browser. What does this have to do with Dwarf Fortress? There’s tons of generic solutions like this that would work the same way for DF as well. It’s giving AI slop.

Re: Dwarf Fortress in the Browser

#9
post #4

Honest question. Do people read these massive vibe-coded README.md files, or are they just artifacts? The minute I see them, I tune out and move on. These types of docs come across to me as so over-specified and memorialized that I just find it not worth the effort to read. Of course for legacy projects this type of documentation would have been invaluable. What's changed, I wonder?

You have. The words in the file still convey useful information, but because theres a particular writing style, you've deemed the words unimportant to read. If you went to a lecture about some topic you were interested in, but as soon as the speaker started talking, they sounded gay, and then you got up to leave because you just can't stand that, is that on you or them? Because the AI culture war of it's coming to take your job, so you'd better detect when something is made by AI, otherwise you can't enjoy it. Calling out every instance where AI is slightly off is a good thing to do. Because it'll be used to make the machines better at not doing that.

Coke Zero is good these days.

Re: Dwarf Fortress in the Browser

#10
post #4

Honest question. Do people read these massive vibe-coded README.md files, or are they just artifacts? The minute I see them, I tune out and move on. These types of docs come across to me as so over-specified and memorialized that I just find it not worth the effort to read. Of course for legacy projects this type of documentation would have been invaluable. What's changed, I wonder?

My eyes just glaze over when I see every file being listed and its purpose. Just because you CAN do that with LLMs doesn’t mean you should. What are you really trying to communicate?
Post reply on HN