News for hackers. Stuff that matters.

jostmon

You seem to be presupposing that all, or much of the C/C++ written today will follow best practices and be written by "expert" programers. A portion will, perhaps even a substantial portion, but I'd be willing to wager a far larger portion of the Rust written today will follow best practices and doesn't have to be written by expert programers. This is because the safety in Rust isn't optional, like it is with C/C++ best practices/new features.
Re:Author of “Unix in Rust” Abandons Rust in Favour of Nim on Sunday February 15, 2015 @12:48PM (#9053315)
Have you read the following article?

https://gradha.github.io/articles/2015/02/goodbye-nim-and-go...

I'm curious about your thoughts on it being that the author speaks about some areas you're currently talking about.

Re:Author of “Unix in Rust” Abandons Rust in Favour of Nim on Sunday February 15, 2015 @12:47PM (#9053314)
> The number of compiler bugs is a bit scary.

This is actually one of the things that keeps turning me away each time I try Nim. All software has bugs, got it, but in my mind a language nearing 1.0 should squash some of that list (or remove/feature gate things causing them) before even thinking about a 1.0 IMO.