Doom in Django: testing the limits of LiveView at 600.000 divs/segundo
33 points
3 days ago
| 4 comments
| en.andros.dev
| HN
kvakvs
26 minutes ago
[-]
Since Doom renders the image with vertical columns of pixels (floor, lower wall, portal if exists continues rendering the other sector, then upper wall then ceiling) and since browsers are very good at drawing the sprites out of larger textures... You could send vertical divs shaded with the sector light level and picking the correct textures. Instead of hundreds per column you will have like 5 divs on average per column and they will be textured shaded and scaled by the browser?
reply
agentifysh
1 hour ago
[-]
if only i could run django on cloudflare workers

guess i could run it on a dedicated server

would be nice if we can get django and liveview working without a server

reply
evilmonkey19
10 minutes ago
[-]
I wish we could host Django apps with the tasks and everything on Cloudflare workers. Also it would be nice to have a DB like SQLite within Cloudflare.
reply
leobuskin
1 hour ago
[-]
you can do it on wasmer's workers, their last wasm/python approach is pretty solid (compatibility, performance). it's sad to say, but after 4 years of "beta" Python support on CF workers - it's still ugly. I dunno who was responsible for such a neglect, but even with the last changes - total fiasco
reply
ksec
3 days ago
[-]
In the blog post it uses "600,000 divs/second!" and "10,000 divs using its template engine" while the heading uses 600.000.

I assume the difference in usage of full stop / period or comma is accidental?

reply
andros
3 days ago
[-]
Yes, you right hehe. I had fixed!
reply
pawelduda
1 hour ago
[-]
Shame Phoenix LiveView is missing from the comparison
reply
leobuskin
1 hour ago
[-]
It's only django-related third-party packages comparison (and SSR itself), would be a bit strange to compare with a different language/stack and/or framework
reply