3 ms·
I think people undersell the value of safety. Back in the 80's and 90's, it wasn't uncommon to drop into assembly to grab every last cycle of performance, sinc
by tombert 7y ago
I think people undersell the value of safety. Back in the 80's and 90's, it wasn't uncommon to drop into assembly to grab every last cycle of performance, since computers were so slow. We also didn't do garbage collection, and people were writing in languages like C and C++. Software from then was also prone to random crashes and freezes, which doesn't happen so much anymore.
We've started to come around with languages like Rust, but a lot of engineers have (in my opinion rightly) come to the conclusion that it's better to abuse the faster speed of computers to have a higher assurance of the software being correct. Could I conceivably get better performance if I wrote something in C and wrote a custom allocator? Maybe, but I'd probably make a mistake, and my GC'd language is fast enough for most of what I do.
- hgoel 7y agoOne can have safety without the absurd bloat though.
- tombert 7y agoI agree with you in theory (hence why I gave a nod to Rust), but I think it's easier to have safe, bloated software. I think newer languages like Rust and Swift definitely are demonstrating the ability to have lean software that is just as fast as something written in C, but these are still relatively new in the scope of things. Much as I think Java is a garbage language, there's no doubt that, by default, it's safer than a program written in C. It also typically is bigger, requiring a bit more RAM and resources.
- pjmlp 7y agoCheck DoD's security report about Multics and how it avoids typical UNIX exploits thanks to PL/I instead of C.
- pjmlp 7y agoBack in those days some of us were actually using compilers for Pascal dialects, Basic dialects, with C and C++ being yet another set of languages. Then C++ started to gain market share on OS/2, Windows, BeOS, Epoch, macOS, Newton as the way to write UIs, even if their kernels and low level APIs were written in C, or C with C++ compiler style. All C++ libraries bundled with compilers, provided strings and vector types with bounds checking. It was the rise of C's adoption thanks to FOSS that brought the unsafety wrath upon us.