From: Austin Ziegler <halostatue@...>
Date: 2006-07-06T21:00:15+09:00
Subject: Re: debugging proposal

On 7/6/06, Alexandru Popescu <the.mindstorm.mailinglist@gmail.com> wrote:
> On 7/6/06, Joel VanderWerf <vjoel@path.berkeley.edu> wrote:
>> You're not going to like this response, but after ruby sinks in and gets
>> in your veins, this is how you debug:

>> 1. refactor
>> 2. unit test
>> 3. write to stdout / stderr / log files
> I haven't done too much real work on ruby yet, but I still believe
> this is a very bad suggestion.  Ruby (and any programming language) is
> about productivity and in my whole experience (I have to agree that
> most of it is spent on Java) never a sout have been more productive
> than a debugging session (for enough complex stuff).

I think you misunderstood. This isn't a suggestion. It's just how one
ends up debugging most of the time. Frankly, I think I have missed a
graphical debugger exactly once in my Ruby programming. Everything
else has been easier to deal with with judicious use of tracers and
logging.

-austin
-- 
Austin Ziegler * halostatue@gmail.com * http://www.halostatue.ca/
               * austin@halostatue.ca * http://www.halostatue.ca/feed/
               * austin@zieglers.ca