I guess this is trolling, but I've never claimed credit for the traditional coding part.

The unique bits I did do

- Checked the specs for actual hardware limits, DMA and any acceleration

- A magic dither based on my previous (normally coded) older projects (see GitHub)

- Image width "compression" idea with loss reduction using sharpening and a slight aspect change.

- Optimising DMA size chunking for optimal memory transfer.

- A lot of actual manual testing, including sheer reduction, frame rate testing, and multiple resolution and different monitor tests (and I lost one - the HDMI port no longer works on my old Celcus)

Failed experiments with:

- using the onboard secondary controller to bypass the primary controller limitations

- devising a hack that would use the vertical scan horizontally using monitor rotation

- attempting an 8, not 16/32 bit desktop for higher performance (old school technique).

- investigating non hardware hacks for overclocking the onboard chips.

- fixing a KVM issue, that required multiple physical disconnects and reconnects to replicate, and a significant amount of weekend time.

So yeah, vibe coded, because I'd never have been able to try these ideas in such a short timescale if I hadn't.