3 ms·

mostly true. it took me a while to decide, I eventually picked up c++. modern c++ is very different nowadays, and it keeps evolving fast, to some extent many m

by ausjke 6y ago

mostly true. it took me a while to decide, I eventually picked up c++. modern c++ is very different nowadays, and it keeps evolving fast, to some extent many modern languages are having the same new features, c++ is becoming better and better for each new standard release, and g++/clang++ also keep up with new sanitizer, static analysis, excellent warning optional flags etc, in fact it is now very hard to make those stupid mistakes these days with modern c++ in a good IDE(even vim with the right configuration). I will keep my eye on rust, I use a few rust utilities myself, but for the heavy duty of my carerr, c/c++ remains to the the top choice.

saagarjha 6y ago
C++ does however still leave the door open for the not-so-stupid mistakes that are still memory safety issues ;)
pizza234 6y ago
> in fact it is now very hard to make those stupid mistakes these days with modern c++ in a good IDE(even vim with the right configuration). Google has, supposedly, some of the best engineers¹ in the world, and the best tooling in the world, and they keep pouring tons of resources on the best engineers and the best tools. Yet, the same memory safety errors (which Rust, or any hypothetical memory-safe language, prevent entirely) keep popping again, and again. Have you heard of CVE-2020-0022? It's amazing. In this perspective, pouring resources and effort on those languages is like trying to open a door by banging the head harder. It's fine if you like it, just don't pretend it's the optimal way to open doors. ¹=edited, to make it clearer what I wanted to convey.
- Koshkin 6y ago
  > Google has, supposedly, the best engineers in the world I would say, it's SpaceX. (I wonder what they code in.)
- ausjke 6y ago
  Thanks. I have not done android for the last year, but I'm repo-sync now to see CVE-2020-0022 can be captured by the g++ flags I had now
ausjke 6y ago
https://youtube.com/watch?v=iOBXVOAbpdY https://youtube.com/watch?v=iOBXVOAbpdY this is a 8-minute study on how rust is safe comparing to C, the summary is that, there is a long way to go, many rust code is still unsafe today.

by ausjke 6y ago

saagarjha 6y ago

C++ does however still leave the door open for the not-so-stupid mistakes that are still memory safety issues ;)

pizza234 6y ago

> in fact it is now very hard to make those stupid mistakes these days with modern c++ in a good IDE(even vim with the right configuration). Google has, supposedly, some of the best engineers¹ in the world, and the best tooling in the world, and they keep pouring tons of resources on the best engineers and the best tools. Yet, the same memory safety errors (which Rust, or any hypothetical memory-safe language, prevent entirely) keep popping again, and again. Have you heard of CVE-2020-0022? It's amazing. In this perspective, pouring resources and effort on those languages is like trying to open a door by banging the head harder. It's fine if you like it, just don't pretend it's the optimal way to open doors. ¹=edited, to make it clearer what I wanted to convey.

Koshkin 6y ago
> Google has, supposedly, the best engineers in the world I would say, it's SpaceX. (I wonder what they code in.)
ausjke 6y ago
Thanks. I have not done android for the last year, but I'm repo-sync now to see CVE-2020-0022 can be captured by the g++ flags I had now

ausjke 6y ago

https://youtube.com/watch?v=iOBXVOAbpdY https://youtube.com/watch?v=iOBXVOAbpdY this is a 8-minute study on how rust is safe comparing to C, the summary is that, there is a long way to go, many rust code is still unsafe today.