https://github.com/mikroverk/esp32sim#boards-esp32-s3
… are just too much with their dense mix of formatting, brackets, semantic punctuation, command line arguments and part numbers etc. (This one is particularly absurd but it's not the only one).
I may be middle-aged now and a non-expert but I am pretty sure these things are generally exhausting to even expert young readers. I would urge you to reconsider how this page is presented.
1) As long as a novel.
2) Poorly formatted.
3) Has several claudisms in each sentence.
It’s also a predictor of the level of slop in a project since it is getting worse with the people talking about “code quality” have now vanished and are no where to be found.
I’ve been working on esp32sim, an open-source ESP32 emulator that runs in the browser.
The fun part of the demo is that there is no ESP32 involved — the firmware is executing in the emulator.
The goal is to make ESP32 software easier to experiment with, test and simulate without always needing physical hardware connected.
Source: https://github.com/mikroverk/esp32sim
I made a short video showing it in action: https://youtu.be/waoWFilTWEc
I’m particularly interested in feedback from embedded developers: what would an emulator like this need to support before you’d actually use it for development, testing or CI?