News for hackers. Stuff that matters.
Re:A whole boss fight in 256 bytes by philxor on Tuesday April 07, 2026 @09:31PM (#47683666)
And it came in 5th place in the competition. The winner was this one which is 16 bytes...

https://www.youtube.com/watch?v=QKLhH_ANwIc

Re:A whole boss fight in 256 bytes by omoikane on Wednesday April 08, 2026 @12:52AM (#47685434)
Re:A whole boss fight in 256 bytes by HellMood on Wednesday April 08, 2026 @03:08AM (#47686420)
The demoscene has a curated collection of "best 16 bytes ever" https://nanogems.demozoo.org/#16_byte_intros As well as 32,64 and so on ... It even goes down to 8(!) Byte productions
Re:A whole boss fight in 256 bytes by tromp on Wednesday April 08, 2026 @03:15AM (#47686466)
You can do amazing things in 8 bytes [1].

[1] https://tromp.github.io/blog/2026/01/28/largest-number-revis...

Re:A whole boss fight in 256 bytes by HellMood on Wednesday April 08, 2026 @03:25AM (#47686565)
You can (on real MSDOS!) go as low as 6 bytes

https://www.pouet.net/prod.php?which=63538

But most people wouldn't find that visually satisfying

The technical details why this works are very interesting though :)

Re:A whole boss fight in 256 bytes by senfiaj on Wednesday April 08, 2026 @06:50AM (#47688347)
I guess anything that is less than 7 bytes can be brute forced.
Re:A whole boss fight in 256 bytes by HellMood on Friday April 10, 2026 @07:21AM (#47716414)
Well, it would be 2^(7*8) = 72057594037927936 possible intros. Someone/something has to generate, run and evaluate them all. Theoretically it's the "halting problem" all over, to wait for the "final output" of each intro. The 16 byte effect for example takes a while to achieve its final form. So even if it is somehow managed to evaluate 1000 intros per second, we are looking at about 2 million years of time to really test ALL possible 7 byte intros.
Re:A whole boss fight in 256 bytes by senfiaj on Sunday April 19, 2026 @07:48PM (#47828793)
I think there are some standard header bytes, so the number of combinations of the interesting parts might be much smaller. Also I said less than 7 bytes, so it's actually 281474976710656 . If header bytes reduce 1 or 2 bytes, it will be 4294967296 - 1099511627776. 1099511627776 / 1000 / 60 / 60 / 24 / 365 is around 35 years.