2 ms·
> But BIND isn't just failing because "it's written in C", it's failing because it's written in terrible C. That said, "terrible C" is probably most every C rou
by bsder 10y ago
> But BIND isn't just failing because "it's written in C", it's failing because it's written in terrible C. That said, "terrible C" is probably most every C routine written by someone with less than 10 years of solid low level experience, so "writing good C code" is not very scalable.
Please do remember that many of these codebases are ancient.
If you rewrote many of these in C today, they would be much better--especially if you also added a test suite around them.
I'm happy to see this in Rust as I'd like Rust to get some real, hostile-environment usage to see what breaks.