4 ms·
Sure. Why purchase a H200 if you can go with an ESP32 ^^
by micw 8mo ago
Sure. Why purchase a H200 if you can go with an ESP32 ^^
- sigmoid10 8mo agoBlowing 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.
- __tnm 8mo agoyeah 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
- pitched 8mo agoDoom 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 8mo agoyah my back of the envelope math.. the “app logic”/wrapper pieces come out to about 25kb WiFi is 350 Tls is 120 and certs are 90!
- oso2k 8mo agoMaybe you’re misremembering or referring to Doom (2016). The original Doom was developed for DOS and id had to build a lot of its own network stack. BSD style socket based networking wasn’t a given in DOS. Still, zclaw is an impressive achievement.
- epcoa 8mo ago> 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.
- madduci 8mo agoThe whole ESP32 Libraries are kind of bloated. To enable Bluetooth, WiFi or HTTP handling, you need to embed some large libraries