Regarding #libsibo, I'm trying to decide on the way forward for the project.
Currently it's in #Arduino C, so there's the odd class, but it's mostly regular C. It'll run on an Uno, ESP32, or a Pico/RP2040.
I've wanted to drop the ESP32 support for ages. But I'm wondering about dropping Arduino support and switching fully to the #RP2040 SDK. For the Uno, I can just maintain the old .INO file for basic functions.
If I go C, I'll have to refactor the classes. But is going full C++ a good idea?
Also, I'd quite like some of #libsibo to be usable on a desktop OS as well as the RP2040.
For example, most of siboimg/fefstool's back-end functions will end up in libsibo (and, in fact, already have), so surely it makes more sense for fefstool to just call libsibo?
I'm sure someone's going to say "use Rust." But my brain can't even handle switching to Go right now, so I think rewriting my current projects in Rust is probably a leap too far.
@thejpster The Rust Signal - a picture of Ferris - is projected into the sky.
A lone, bearded developer looks to the heavens.
He knows what he has to do.
(I found the picture after writing this. Credit to @ekuber.)
The Last Psion | Alex
Jonathan ‘theJPster’ Pallant