| ▲ | sigmoid10 2 hours ago | |||||||
Blowing more than 800kb on essentially an http api wrapper is actually kinda bad. The original Doom binary was 700kb and had vastly more complexity. This is in C after all, so by stripping out nonessential stuff and using the right compiler options, I'd expect something like this to come in under 100kb. | ||||||||
| ▲ | epcoa 3 minutes ago | parent | next [-] | |||||||
> vastly more complexity. Doom is ingenious, but it is not terribly complex IMHO, not compared to a modern networking stack including WiFi driver. The Doom renderer charm is in its overall simplicity. The AI is effective but not sophisticated. | ||||||||
| ▲ | pitched 2 hours ago | parent | prev | next [-] | |||||||
Doom had the benefit of an OS that included a lot of low-level bits like a net stack. This doesn’t! That 800kB includes everything it would need from an OS too. | ||||||||
| ||||||||
| ▲ | __tnm 2 hours ago | parent | prev [-] | |||||||
yeah i sandbagged the size just a little to start (small enough to fit on the c3, 888 picked for good luck & prosperity; I even have a build that pads to get 888 exactly), so i can now try reduce some of it as an exercise etc. but 100kb you’re not gonna see :) this has WiFi, tls, etc. doom didn’t need those | ||||||||