Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
1–10 of 33 posts
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#2Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#3Reminds me a lot of demoscening https://en.wikipedia.org/wiki/Demoscene
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#4Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#5Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#6Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#7Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#8Amazing, considering whole demo fits in URL. Modern website developers should learn a thing or two about optimization from this.
I'm just as anti-bloat as the next HN'er, but optimizing websites is almost certainly not a business interest, therefore not an imperative, and therefore not going to happen. Instead of just wishing web developers were better, it would be more productive to find a way to align website optimization with business interests.
After all, how many people, really, would stop using websites or apps because they're slow? They can be frustrating, but most of the non-tech people I know just deal with it. That's hardly a recipe for changing the way websites are built. Basically, I posit to you that website, webapp, and mobile app optimization is a revealed preference [0], where the preference is that it's not actually important.
Re: Show HN: Attempt to bring a cinematic experience in 256 bytes (WASM)
#9I wonder if someone could port Elevated to WebGL, then how big would it be? I wonder if it would fit within 64KB.