• AnarchoSnowPlow
    link
    fedilink
    English
    arrow-up
    27
    ·
    9 months ago

    I work in embedded systems (more and more test lately though), historically in aviation (not fucking Boeing lol) and test and measurement instruments. So, critical environments. In those situations, when you’re writing bare metal firmware, you never dynamically allocate anything. Everything tends to be accounted for, RAM usage is tightly controlled, there are even points where you’re counting clock cycles for efficiency. We even accounted for radiation based bit flip events, which are incredibly uncommon, but we know they exist so they have to be handled.

    My point is, this is a valid concern in some spaces, but when you use C in a purely functional way, it’s not the loaded gun they portray it as.