Re:The Safe C Library (2009)
by lmm on Thursday April 13, 2017 @10:50AM
(#14107407)
> C is a thin layer over hardware. There is a reason it hasn't yet been replaced despite waves of new, safer, more powerful paradigms and languages.
C has already been replaced in what would have been the vast majority of its use cases 20-30 years ago, especially if we're talking about new code. At this point it's mainly alive due to inertia.
> If you need to get your code on a 8/16/24 and even most 32 bits microcontrollers, there is not a lot of choice.
Rust is starting to get some microcontroller support. And in many cases the business case has shifted away from true microcontrollers - there's no longer much or any price advantage over a proper ARM (for example), battery technology is getting better all the time...
> virtually all the hardware you own has most -if not all- of its code written in C/C++.
I don't think that's true these days. My phone is running a certain amount of C in its low-level OS, sure, but that will be dwarfed by the amount of userspace code it's running that's written in Java or similar.
C has already been replaced in what would have been the vast majority of its use cases 20-30 years ago, especially if we're talking about new code. At this point it's mainly alive due to inertia.
> If you need to get your code on a 8/16/24 and even most 32 bits microcontrollers, there is not a lot of choice.
Rust is starting to get some microcontroller support. And in many cases the business case has shifted away from true microcontrollers - there's no longer much or any price advantage over a proper ARM (for example), battery technology is getting better all the time...
> virtually all the hardware you own has most -if not all- of its code written in C/C++.
I don't think that's true these days. My phone is running a certain amount of C in its low-level OS, sure, but that will be dwarfed by the amount of userspace code it's running that's written in Java or similar.