So tired of these types of articles. It isn't a problem with C. It's a problem with pack of due diligence, shoddy specification, opaque HW/software boundaries,

So tired of these types of articles. It isn't a problem with C. It's a problem with pack of due diligence, shoddy specification, opaque HW/software boundaries, and not checking one's assumptions. The abscence of analyzers, or implementation quirks of different compilers are eschewed as a non-concern to the programmer by the mainstream professional tech community. Abstraction, they say, is the key and solver of all problems. I happen to reject this view. It's taken me well over a decade to even approach being able to take a stab at knowing what is up with an executing program from the top, down to the hardware. When I lament that this is not a more common phenomena (knowing all/most of your abstraction layers such that you can make well grounded statements in the physical sciences sense), I get looked at by peers like a nut. I thought we were all here to make things we can all reasonably say we understand how it works... That's what I thought Engineers did...