> have actually been harmed by the presence of features in the language
I am harmed routinely by too many features. I've been coding C++ for 11 years and I still end up scratching my head when I end up in foreign territory. Even his code at the end of the article which I think is supposed to be illustrating some kind of simplicity looks like a giant hairball of mess to me. I've ended up devolving to using a small subset of C++ features in my code which I know inside out and is sufficient for my needs. Others all seem to do the same but they arrive at a different subset. Java on the other hand seems to be so feature deprived and simplistic (minus generics, but they are almost an anti-feature) that no matter whose code I look at it is extremely obvious what is going on.
I spent almost as much time learning advanced C++ as I did unlearning it and going back to KISS. Even then, I still had to deal with code from people who were stuck in the advanced stage.
Re:C++11 Makes Competitors Go Rusty
by anonymoushn on Wednesday February 01, 2012 @06:13PM
(#3540559)
Can I just trade in my exceptions for Maybe or Either? It's already possible to do both of these things, the trouble is that I have to use other people's code that uses exceptions.
Re:C++11 Makes Competitors Go Rusty
by evincarofautumn on Wednesday February 01, 2012 @07:22PM
(#3540819)
Except the C++ dragon rears its head. How do you build an intelligent Maybe or Either type in C++? Should they be value types containing unions? You can’t use “non-trivial” types in unions till C++11, and a lot of people haven’t yet upgraded. Referential types with dynamic allocation? How do you transfer ownership? Are “Left” and “Right” subtypes of “Either”? It’s ridiculous.
Re:C++11 Makes Competitors Go Rusty
by SamReidHughes on Wednesday February 01, 2012 @09:40PM
(#3541193)
The choices are clear for every situation you describe.
Re:C++11 Makes Competitors Go Rusty
by evincarofautumn on Wednesday February 01, 2012 @11:03PM
(#3541364)
To you, to me, but not to most C++ users. Yeah, these types should be in a library, but that’s not the point. A programmer shouldn’t have to be on par with the Boost writers to make something this conceptually simple. I’ve used C++ as my primary language for years and only now can I speak with authority on the finer points of the language. It’s quite powerful, but so unpleasant.
Re:C++11 Makes Competitors Go Rusty
by drivebyacct2 on Wednesday February 01, 2012 @04:41PM
(#3540119)
No offense, but have you spent much time with Go or Rust? In most cases Go's performance difference isn't extremely divergent from C++'s and it preserves safety and enhances convenience, exceptions and adds concurrency.
Re:C++11 Makes Competitors Go Rusty
by SamReidHughes on Wednesday February 01, 2012 @08:19PM
(#3540995)
Go afaict does more than preserve safety, it improves it! And it enhances convenience. Concurrency in C++ works just fine, though.
Last I heard the Go compiler was generating code 6x or more slower than comparable C++ code. Is that not still true?
You heard wrong: http://blog.golang.org/2011/06/profiling-go-programs.html
Re:C++11 Makes Competitors Go Rusty
by andrewcooke on Wednesday February 01, 2012 @09:20PM
(#3541155)
The graphviz / svg output from the profiler shown there is very nice. Does something similar exist for other languages? I particularly like the scaling of the node size by the appropriate value (CPU time, memory use, etc).
Go's pprof is based on the C-based one: http://code.google.com/p/gperftools/
If you want a less complicated language than C++11, other than some low-hanging white noise inherited from C, you'll probably have to give up safety, convenience, performance, or exceptions.