News for hackers. Stuff that matters.
Re:Go 1.19 Released by pjmlp on Tuesday August 02, 2022 @04:03PM (#32323589)
Not on our lifetime, but reducing the use cases that require their uses helps.

This is also why I follow GraalVM since the days it used to be MaximeVM.

Re:Go 1.19 Released by staticassertion on Tuesday August 02, 2022 @04:04PM (#32323600)
I personally have no issue with C++ being used for compilers, but to each their own.
Re:Go 1.19 Released by pjmlp on Tuesday August 02, 2022 @04:06PM (#32323622)
Depends on how one stands in regards to secure code.

I love C++, but secure like the ALGOL linage it will never be, no matter how many fixes we throw at it, because that C copy-paste compatibility layer is never going to be thrown away.

Re:Go 1.19 Released by staticassertion on Tuesday August 02, 2022 @04:09PM (#32323661)
I'm quite fond of secure code but attackers don't really exploit memory unsafety in compilers as they're not often in a position to or, if they are, there are much simpler ways to execute code.
Re:Go 1.19 Released by pjmlp on Tuesday August 02, 2022 @04:11PM (#32323696)
Except compilers aren't used in isolation, if one writes the compiler toolchain in C++, chances are other system critical components are also written in C++, if nothing else for the comfort of single language use.

Security must be applied end to end, and not pontual.