I'm just going to respond to the top part of your post, as it's at least somewhat relevant rather than being a disconnected rant about the kids censoring you.
> I am just hooking linux kernel calls, I will never take JS for this. Pure C.
Why not? Hooking native code in other languages is already fairly common: http://www.cycript.org
> Valgrind? I have a header with #define MALLOC/FREE/REALLOC/... which returns larger buffer with guards at beginning and the end while after 25 years of C I hardly do anything more problematic that this.
Valgrind does significantly more checks than your solution.
> System language? Make it.
"Systems language" is a very ill-defined term, often used to gatekeep people.
> If it is just a newage nonsense wasting resources for the sake of deallocating and taking care about buffer boundaries as it is so hard to take care and track your memory I will skip it.
Keeping track of your memory is hard. If you say "no, it's easy for me", I'd like to see a non-trivial sample of your code that doesn't have memory safety issues.
It is easy for engineers, because engineers are trained to make things correctly even when that is inconvenient.
Engineers make bridges that don't collapse (unless not maintained for decades) and planes that don't fall from the sky (unless overruled by management). By the evidence, it is not easy for people who just can't be bothered to take the time to make anything correctly.
So, there are languages for engineers to use to make things where it matters if they are right, and languages for everybody else, where apparently it doesn't. Now, all we need is for engineers not to need to call into libraries not written by engineers.
> I am just hooking linux kernel calls, I will never take JS for this. Pure C.
Why not? Hooking native code in other languages is already fairly common: http://www.cycript.org
> Valgrind? I have a header with #define MALLOC/FREE/REALLOC/... which returns larger buffer with guards at beginning and the end while after 25 years of C I hardly do anything more problematic that this.
Valgrind does significantly more checks than your solution.
> System language? Make it.
"Systems language" is a very ill-defined term, often used to gatekeep people.
> If it is just a newage nonsense wasting resources for the sake of deallocating and taking care about buffer boundaries as it is so hard to take care and track your memory I will skip it.
Keeping track of your memory is hard. If you say "no, it's easy for me", I'd like to see a non-trivial sample of your code that doesn't have memory safety issues.