I really want to rid the world of memory bugs, so you think I would agree with TFA. But unless he includes situations where you must have zero dependencies (be

I really want to rid the world of memory bugs, so you think I would agree with TFA. But unless he includes situations where you must have zero dependencies (besides what is already expected to always exist, like a C compiler) among the situations where you have no other choice, then I disagree with him. My last project and my current project are both in C. I hate that that's necessary, but the truth is that C is supported basically everywhere. It means that I can claim zero dependencies because it's de facto true, in that no user has to go and find other things to make my software work. For example, if I wrote in Rust, the user would have to install Rust if they don't have it already, so I would consider that a dependency. Of course, the fact that I am writing in C means that memory bugs can happen, so I had to have a plan for getting rid of them before release, and I do. (See [1] for an example.) I guess what I am trying to say is that there's (unfortunately) still a place for C, and that (unfortunately) that place may be bigger than at first glance with the existence of things like Rust. And I think that will remain true until Rust or some other competitor is as ubiquitous as C. [1]: https://git.yzena.com/gavin/bc/src/branch/master/manuals/development.md#user-content-fuzzing-1 https://git.yzena.com/gavin/bc/src/branch/master/manuals/dev...