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.
[ Parent
| on HN ]
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/