Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by natsucks on Thursday October 05, 2023 @03:42PM
(#37783312)
What's holding me? People writing software who are choosing C/C++ for legacy reasons only.
[ Parent
| on HN ]
Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by JohnFen on Thursday October 05, 2023 @03:55PM
(#37783484)
When I use C or C++, it's certainly not for legacy reasons. And my use of it doesn't prevent you from using a different language.
Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by FpUser on Thursday October 05, 2023 @04:10PM
(#37783670)
I do not use C++ just for legacy reasons. And frankly I do not give a flying fuck about holding people like yourself. You are free to do as you please, do not expect others to provide for you.
Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by prosqlinjector on Thursday October 05, 2023 @03:53PM
(#37783450)
Currently employed writing new C++ btw.
Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by omgmajk on Thursday October 05, 2023 @05:08PM
(#37784316)
Currently employed writing new C btw. It's not holding me back one bit.
Re:Safety vs. Performance. A case study of C, C++ and Rust s...
by Conscat on Thursday October 05, 2023 @05:02PM
(#37784270)
Other languages need tooling and featurefulness that is overall on par with C++ first. So far no low level language has profilers and debuggers that are as good, none have nearly as many compiler hints, and most are far harder to write zero overhead abstractions in.