On Monday, 18 March 2013 at 19:39:38 UTC, Walter Bright wrote:
On 3/18/2013 12:08 PM, Paulo Pinto wrote:
Am 18.03.2013 13:21, schrieb Andrei Alexandrescu:
On 3/18/13 1:46 AM, Rory McGuire wrote:
The reason I use golang and not dlang for development at
work is because
debugging is straightforward no weird segfaults after you
program has
been running for a couple of days.
Their debugging and benchmark tools are really good and the
documentation is fantastic.
Could you please go into details on the debugging and
benchmarking
tools? Thanks.
From the time I used Go.
You can use gdb or if you prefer something like a debugger
IDE, LiteIDE
http://code.google.com/p/liteide/
For benchmarking there is an old blog entry about the tools.
http://blog.golang.org/2011/06/profiling-go-programs.html
Nothing that you cannot find in other languages, unless there
is now something
much better available.
dmd has the -profile, to automatically generate a profile
report, and -cov, to tell you which lines were executed and how
many times.
That was my point.
I was initially attracted to Go given its similarity with Oberon
concepts and was even enthusiastic to try to contribute something.
However the way some Go concepts are sold as being new, while
other languages outside the C world have had them for years, and
the resistance of Go community to anything new look elsewhere.
This answer from one of their developers is a good example,
http://9fans.net/archive/2008/08/134
--
Paulo
