57 bytes (36 days ago): https://news.ycombinator.com/item?id=42348294 61 bytes (2024): https://news.ycombinator.com/item?id=38962792 67 bytes (2023): https://news.ycombinator.com/item?id=38060165 85 bytes (2023 - Popular, 134 points, 24 comments): https://news.ycombinator.com/item?id=36999463 89 bytes (2023): https://news.ycombinator.com/item?id=36940010 100 bytes (2023): https://news.ycombinator.com/item?id=36933804…
Snake Game in 56 Bytes
11–16 of 16 posts
Re: Snake Game in 56 Bytes
#12Re: Snake Game in 56 Bytes
#13Repo has 400+ commits, granted a lot of them are for web demo etc, but this just highlights that sometimes doing really small amount of anything (world limit on peer reviews, anyone?) is often a lot of work
For example, this commit seemed like a lot of work to save a single byte: https://github.com/donno2048/snake/commit/bd6bcb1a1477f28130...
Re: Snake Game in 56 Bytes
#14Re: Snake Game in 56 Bytes
#15Has anyone gotten this to work on an actual PC? It runs way too fast, even on an original XT (I'm guessing the keyboard controller isn't the same as js-dos).
Re: Snake Game in 56 Bytes
#16Has anyone gotten this to work on an actual PC? It runs way too fast, even on an original XT (I'm guessing the keyboard controller isn't the same as js-dos).
Adding in a 100k iteration or so busyloop to the beginning of the food segment should do the trick and only add a few bytes. You could do something fancy with the clock interrupt, which is a bit more portable and stable, but might cost a few more bytes.