A 1 square meter solar panel that weighs around 10kg contains under half a kg of actual doped silicon photovoltaic cells, with the remaining >95% being mainly aluminium framing, glass to cover the cells, and some backing material and wiring, all of which are trivially recyclable. So even if the doped silicon wasn't recyclable (which it is with a little more effort than the other materials) that's hardly the majority of the material that goes into making a solar panel.

I agree it's a bit annoying, but a better solution than using `as` is just telling reduce what its generic type should be:

tasks.reduce boolean>>((acc, item) => ..., {})

Also imo it's cleaner to reduce to an object with something like this as the callback:

(acc, item) => ({ ...acc, [item.label]: t => t.label === item.label })

oh man I somehow never realized I could just use that square bracket syntax. must update everything

Any reason why you didn't just use ESPHome for the firmware?

It even has a component specifically for the ULN2003 stepper motor driver you were using

https://esphome.io/components/stepper/#uln2003-component

Truth be told, while I had known about ESPHome while working on this project, for some reason, I just felt the urge to hack together my own firmware.

It might've been because my early testing was done via an old Arduino Uno board, and I must've figured that I might as well port the sketch over to the ESP32 once I had it working.

(I'm general though, I will say that LLMs can totally write bespoke one-off firmwares like this, and I don't feel too bad about it, given that it's running entirely within my LAN, and will never actually get "productized")

I wonder if it would be possible to get ZMK working on it instead, since that's built primarily for wireless support, and also supports wired configurations too as of recently. Seems like the STM32 that the Q6 pro uses is supported, so you might have some luck: https://zmk.dev/docs/hardware