HackerTubewatch
Surprise me
Frame from puls (256 bytes) Plays via YouTube's privacy-enhanced embed

puls (256 bytes)

JanRrrolaKadlec
Demos
YouTube
1 HN user recommended this demo1 month2011–2014 score 1
Years with an HN recommendation, 2007–2026

HN commenters cite it as the most impressive 256-byte production and as an example of how much graphics code can fit in a tiny binary.

A 256-byte MS-DOS intro that renders a raymarched, procedural 3D animation. It won the 256-byte competition at Riverwash 2009 and the scene.org award for best technical achievement that year, and the author published commented x86 assembly source.

“The most impressive to date is probably Puls” (HN, 2011)

1 recommendations · 2 citations · Demos

3 Hacker News comments

From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.

@psykotic Aug 2011 Recommends
on HN thread Low-level x86 code compression for 64k intros
Neat hack! But stacking sine waves with a bit of modulation isn't exactly earth-shattering. You might like to try some of these: [link] . The most impressive to date is probably Puls: [this video] . The top three 256b productions on Pouet are all doing the same basic thing of ray marching against an isosurface. The sophistication of the geometry has increased a lot since Lattice, which used something simple like cos(x)^2 + cos(y)^2 + cos(z)^2 = f(t) where f(t) is an oscillatory function of time that controls the thinning and fattening of the lattice.
Most impressive 256-byte production to date.

Citations, criticism and jokes

@chengsun Apr 2014 Cites it
on HN thread Evolutionary algorithm to find Quake III's fast inverse square hack with Python
Řrřola (a famous demoscene coder [1]) found a far better constant than the original (a 2.7-fold accuracy improvement) by using an optimisation algorithm over all three constants present in the original inverse square hack. His algorithm and the result (along with a plot of relative error) can be found on his blog [2]. [1]: See, for example, this 256-byte raycaster [this video] [2]: [link]
Example of the coder's 256-byte raycaster.
@userbinator Oct 2014 Cites it
on HN thread Intel Underestimates Error Bounds by 1.3 Quintillion
> You really don't want to use x86 hardware transcendental instructions ...unless you're doing size-optimised graphics intros, where tremendous accuracy is not essential and the stack-based nature of x87 makes for some extremely compact code: [link] [this video] I think the main reason why this issue hasn't been so significant is that the majority of code that uses those instructions isn't dependent on extreme accuracy - code that does would likely use their own routines and/or even arbitrary-precision arithmetic.
Example of compact x87 code in size-optimised graphics intros.

Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.

Keyboard shortcuts

/
Search
j k
Next / previous video
r
Surprise me
l
Like (video page)
w
Watch later (video page)
?
This help
Esc
Close