From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <60a3e97cf80bd30d853c1791a7f4ee6f@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] debugging p9p threads question
Date: Tue,  2 Aug 2005 17:31:59 -0700
From: Skip Tavakkolian <9nut@9netics.com>
In-Reply-To: <5922eb1cb9702ce5797f91d872a4ecd5@orthanc.cc.titech.ac.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Topicbox-Message-UUID: 729910a6-ead0-11e9-9d60-3106f5b1d025

>> interesting, that's the answer in the supercomputing world too. 
> 
> Interesting.  I'm tutoring high school students in a
> programming contest right now.  They are writing their codes
> with emacs/vi and running their MPI jobs on Origin 2k.
> 
> One of the contestants told me .NET was a far better interface
> for programming, which included everything like editor,
> compiler, debugger, online manuals and what not.
> 
> Actually, he even showed me debugging fruently on .NET.
> I rather felt old then...
> # no flame intended
> -- 

It has been my experience that IDE's (including things like Eclipse)
add as many problems as they "solve" with their interfaces.  Also,
they're not universal; e.g.  try to do Windows driver debugging with
Visual Studio.  Guess what works?  printing to the console.

Acid is about the best idea I've seen.