Earlier quoted context omitted.
This is demoscene, it won first place: https://www.pouet.net/prod.php?which=96944
So we're doing WASM demos now?
What's wrong with that?
Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
11–20 of 33 posts
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#12Amazing, considering whole demo fits in URL. Modern website developers should learn a thing or two about optimization from this.
[deleted]
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#13I wonder if someone could port Elevated to WebGL, then how big would it be? I wonder if it would fit within 64KB.
There was a Javascript port of Elevated in about 13KB, but seems it disappeared from the Internet.
Here it is in 28KB. The site also links to a 9KB version (but it didn't work for me):
http://creativejs.com/2013/02/elevated-a-beautiful-mountain-...
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#14Very impressive!
Would it be possible to port to x86/DOS, and keep the same code size? Or is there limitation in the WASM aspect?
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#15Very impressive! Would it be possible to port to x86/DOS, and keep the same code size? Or is there limitation in the WASM aspect?
Actually with HellMood (one of the x86 sizecoding wizards the best known for https://news.ycombinator.com/item?id=23002874) we were working on a port to FreeDOS x86/FPU, but the personal time did not allow us to finish the port before the competition deadline. Quoting HellMood "i think now that a decent port is possible".
There are a few advantages of WASM/MicroW8 like ability to draw vertical lines, or a palette that can use 8bit RGB (while VGA has 6bits), but the x86 in 16bit real-mode has powerful short CPU and FPU instructions, and you can use code as data (e.g., for IEEE float constants) to further reduce the binary length.
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#16I was at Outline Demoparty last night where this was in the compo and we were all blown away. The crowd went proper mad, hats off.
Everybody was already super impressed when it was just sea waves, because they looked much better than one would expect in a 256b compo. And when the weird egg thing came and exploded, our minds did too.
Deserved win!
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#17Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#18256 bytes ?!? How is that possible. I misread it as 256K initially.
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#19> or click the following link if you have the FireFox browser (Chrome’s implementation of WebAssembly has much worse performance).
Now that is interesting. I've been on the FireFox train for 20 years but I haven't seen a "best viewed in FireFox" tag in a long time. It's a pleasant surprise, but I'm also curious how Chrome has managed to be bad at this.
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#20256 bytes ?!? How is that possible. I misread it as 256K initially.
It’s literally in the link.
A non-specified amount of code in the MicroW8 runtime which isn’t included in that 256 bytes to implement the graphics layer (320x240 256 colors 60hz) and gives you 256 kib of memory.
256 bytes is the “cartridge” to run on this platform with compression.
It’s still extremely impressive because of the creativity of the generative visual effects they figured out how to fit in 256 bytes.