3 ms·
With modern developer tooling, it kind of is. Pick the right language for the right job. You can catch the vast majority of crashes in your code at compile time
by stubish 2y ago
With modern developer tooling, it kind of is. Pick the right language for the right job. You can catch the vast majority of crashes in your code at compile time, to the point where the potential of 'making a mistake' is a statistical improbability. But so many companies just stick with C, and even ignore compiler and static code analysis warnings, because the machismo of their devs protects them much better. Software by companies failing basic risk analysis.
- jayd16 2y agoWhy are we talking about language safety when it was a malformed config? It shouldn't boot with a malformed config, by design. The issues seem to be operational not technical.
- stubish 2y agoWhen parsing the config, the code crashed causing a BSOD. It wasn't even known it was malformed at that stage. A safer language would not let you crash when attempting to parse or validate malformed config. Unsafe languages require remembering and bothering to run extra steps to check your code is safe