I think this article serves as a perfect example of why we should consider moving on from C. The first third of this article is "how to do memory allocation and work with strings".
The bit about OBJ parsing is neat, though.
The bit about OBJ parsing is neat, though.
Good Rust code will also care about memory allocations to the same degree as the C code, the difference is that Rust will help you out in making sure your thinking is correct. My experience is that good systems programming has thinking about memory allocations not as an annoying side issue, but as a main concern.
If you want to talk about performance, you better come armed with numbers. If you don't, you're not writing "high performance" code.
For stuff that you run only for yourself and _always_ executes in a blink of an eye I do agree.
> By robust I mean no undefined behavior for any input, valid or invalid; no out of bounds accesses, no signed overflows. Input is otherwise not validated. Invalid input may load as valid by chance, which will render as either garbage or nothing.
Robust is a baseline for high performance programming.