News for hackers. Stuff that matters.
Re:Announcing Rust 1.20 by PopsiclePete on Thursday August 31, 2017 @06:27PM (#15144509)
That's my main beef with C++. You read a book and it's beautiful - no uninitialized memory, safety, no C arrays/strings, RAII everywhere, it's clean, fast.....then you get to the "real world" and realize that 99% of C++ programmers are pretty f###ing horrible at their job and should've just stuck to naked C because at least then you'd be able to pin-point the bugs easier.

So C++ is a wonderful language - in a world that only exists in the creators' heads, or on committee tables, or on brand-new, post C++03 codebases. Basically - nowhere.

Re:Announcing Rust 1.20 by gcp on Friday September 01, 2017 @04:22AM (#15146964)
Most large C++ code-bases predate C++11, which was really game-changing.
Re:Announcing Rust 1.20 by ryl00 on Thursday August 31, 2017 @09:22PM (#15145435)
But isn't that the case with basically ANY programming language? Once its use becomes widespread, escaping the confines of the highly skilled early adapters, you can be sure a whole lot of dodgy code will be written in it.
Re:Announcing Rust 1.20 by xfer on Thursday August 31, 2017 @10:53PM (#15145756)
Not really, because the language doesn't make it difficult to write dodgy code and gives you no power to easily find such dodgy code. In other safe languages either you simply can't write these kind of dangerous code or it should be easier to catch them with just keyword search. In C++ you need powerful static analysis and some dynamic instrumentation to hopefully catch them.