| +10000 I was literally told in one of the comments i made about how difficult a lot of the changes were, for very little practical gain: "the new API WILL require you to rethink your code the new API WILL be a bit harder to use for Rust newcomers, as they really need to think about lifetimes, mutable aliasing and so on" etc Their argument, of course, was that it was "technically better" anyway, as if that is the bar by which you should make things super painful for your customers and newcomers. ESP non-rust works pretty darn well. But ESP-rust feels like it's just a mess run by folks who simply don't value their customers time. I either use STM32 or NRF exclusively now, and could not be happier. |
I recall we had roughly the same experience. Tried to use the OTA API that was rewritten and it was a disaster. The contributors opinion was atrocious, and we had deliverables to deliver so we ended up just hacking it and using unsafe globals to workaround how opinionated it was.
Ive been developing rust embedded applications for about 5 years, so im not new to it either.
I get people want to be ideologically biased with how they structure code, but a public API should be flexible enough to work in a wide range of situations, and what irks me about it is that there isn't really much benefit, if at all, for the pain, time and money it takes to adjust it.