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.
that's iceland. they don't have potholes, because none of their streets get very old, see exhibit A
I don't have first hand experience with it, I also don't get how it would help me. Maybe I need to look at it some more.
have a look at nix
notion is also not FOSS though. and i had bad experiences with the mobile app when cell service is bad.
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.
I'm aware. I write C++17 and I try to be informed what the best praticed are for whatever version of whatever language I'm writing at the moment. But that's actually a reason to not like C++. It's painfully backwards compatible and what was good pratice isn't anymore because now there's a better one, but that better pratice isn't in anyway enforced because of backwards compatibility. And also I don't like templates, generics are superior to me, but that's a me thing.
well actually... sry i couldn't resist
i think the biggest repo is that of nixos
do i smell milk on the way to spoiling? hmm granted, i might be wrong but i really don't think i am.
Well it made sense! In the 70s, and just doesn't anymore. 🤷
not EVs. public transport. or at least mostly that and a little EVs