Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Date: Mon, 11 Feb 2013 13:04:26 -0500
From: Joan Touzet <wohali@apache.org>
To: dev@couchdb.apache.org
Subject: Re: In-browser debugging with Node.js couchjs
Message-ID: <20130211180426.GA7850@atypical.net>
References: 
 <CAN-3CB+NhFbJC4ZWpt_jJzwPyUp05RK4EQuhD+oL-LRh0-HQ=w@mail.gmail.com>
 <C1BEA06A-04F7-4AB9-9C03-E1566CCD7D61@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C1BEA06A-04F7-4AB9-9C03-E1566CCD7D61@apache.org>
User-Agent: Mutt/1.5.21 (2010-09-15)

I immediately think: is sandboxing a concern?

Also, this is a test email to see if my MUA is configured correctly,
please (mostly) ignore.

-Joan

On Mon, Feb 11, 2013 at 03:44:57PM +0100, Jan Lehnardt wrote:
> 
> On Feb 11, 2013, at 15:04 , Jason Smith <jhs@iriscouch.com> wrote:
> 
> > I just pushed more work in my nodejs_couchdb branch.
> > 
> > I have a working in-browser GUI debugger. You can set breakpoints, step
> > through code, inspect data values. This works for any JavaScript code
> > CouchDB runs: map/reduce functions, validate_doc_update, filters, etc.
> > 
> > I put up some quick screenshots and mp4 screencast to show what it's like:
> > 
> > https://jhs.iriscouch.com/files/debugger/debug.html
> > 
> > I would love to hear feedback from people. What are your thoughts?
> > 
> > Me? I think it shows the power of Node.js. It shows possible opportunity
> > cost if we do not use it.
> 
> HOLY SHIT THIS IS HOT
> 
> 

-- 
Joan Touzet | joant@atypical.net | wohali everywhere else