Re:Let’s Stop Bashing C
by pjc50 on Friday December 02, 2016 @09:00AM
(#13088562)
> because you'll know exactly what will happen in the chip and the memory when that code compiles.
.. for the specific chip you've targeted. And possibly even the specific stepping.
And that's assuming that you're diligent enough to manually review all that assembler. Very, very few people are. This is why typesafe code was developed. This is why all those checks exist in Rust. Limitations are good. Limitations are your safety equipment. Assembler is the guy who scrambles up on the roof without tether or hardhat to "get the job done".
> language for which there should be a criminal trial and a prison sentence of several decades
Commentators who overuse hyperbole should be executed.
.. for the specific chip you've targeted. And possibly even the specific stepping.
And that's assuming that you're diligent enough to manually review all that assembler. Very, very few people are. This is why typesafe code was developed. This is why all those checks exist in Rust. Limitations are good. Limitations are your safety equipment. Assembler is the guy who scrambles up on the roof without tether or hardhat to "get the job done".
> language for which there should be a criminal trial and a prison sentence of several decades
Commentators who overuse hyperbole should be executed.