News for hackers. Stuff that matters.
Re:C++11 Makes Competitors Go Rusty by strlen on Wednesday February 01, 2012 @04:30PM (#3540055)
I (shrug) enjoy programming in C++11 and like many concepts in it.

However, there are concepts in Go and Rust that are salient and stand on their own: typeclasses in Go and Rust (concepts, unfortunately, were left out of C++11), rust making std::unique_ptr<> a language feature and support for pattern matching, etc...

While I like support for atomics, memory model, etc.. in C++11, concurrency is still a library in C++. Go and Rust take different approaches to concurrency, but they do make it a _language_ feature which is substantially different.

In short, I hate to bible-thump Paul Graham's article, but this article does remind me of the "blub paradox".

tl;dr I like C++11, but I am glad there are other options (most importantly, Go, and Rust) being developed for userland systems programming.

Re:C++11 Makes Competitors Go Rusty by Arelius on Wednesday February 01, 2012 @04:52PM (#3540182)
I'd like to note that rust does allow mutable shared state, but just in an "unsafe" context, since it is in fact, unsafe.
Re:C++11 Makes Competitors Go Rusty by ootachi on Wednesday February 01, 2012 @05:58PM (#3540504)
Rust has typeclasses as well.
Re:C++11 Makes Competitors Go Rusty by strlen on Wednesday February 01, 2012 @06:08PM (#3540545)
Edited appropriately. Please excuse my ignorance, then. I've only recent began looking at Rust, but I've been playing with Go for some time now. Will have to spend more time with Rust (if only there were more than 24 hours in a day...)