IT’S NOT CORN! IT’S CALLED A THIRST TRAP I’LL HAVE YOU KNOW, UNEDUCATED PIG!
</ sarcasm> (just to be sure)
IT’S NOT CORN! IT’S CALLED A THIRST TRAP I’LL HAVE YOU KNOW, UNEDUCATED PIG!
</ sarcasm> (just to be sure)
laughs/cries in embedded we are currently changing from mbed to zephyr rtos. at the beginning it was decided we will never replace mbed, the thing i am currently replacing, so all the code is using parts of mbed everywhere. there’s not enough space on the chip to have both mbed and zephyr in parallel. yay. you desktop/server/web/whatever people don’t how good you have it.
have a look at nix
As an embedded firmware guy for 10ish years:
C can die in a fire. It’s “simplicity” hides the emergent complexity by using it as it has nearly no compile time checks for anything and nearly no potential for sensible abstraction. It’s like walking on an infinite tight rope in fog while an earth quake is happening.
For completely different reasons: The same is true for C++ but to a far lesser extent.
this is about type 1 diabetes, and i’m assuming you’re talking about type 2