Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Tue, 15 Jan 2013 19:18:13 +0000 (UTC)
From: "Jason Smith (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <JIRA.12627321.1358014485373.139200.1358277493568@arcas>
In-Reply-To: <JIRA.12627321.1358014485373@arcas>
References: <JIRA.12627321.1358014485373@arcas>
Subject: [jira] [Commented] (COUCHDB-1643) Switch to V8
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/COUCHDB-1643?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D13=
554179#comment-13554179 ]=20

Jason Smith commented on COUCHDB-1643:
--------------------------------------

For what it's worth, I wrote a 100% Node.js view server. It's about 200 lin=
es of JavaScript.

https://github.com/iriscouch/couchjs

Actually it just implements `couchjs`. It runs the same "main.js" view serv=
er as the SpiderMonkey one. Only a tiny fraction of the unit tests fail (mo=
stly E4X stuff).

It's quick and dirty. But it makes the point. Node.js is good bang-for-buck=
. What would "V8" bring to the table?
               =20
> Switch to V8
> ------------
>
>                 Key: COUCHDB-1643
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1643
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Jan Lehnardt
>
> I=E2=80=99d like to propose that we switch to the V8 JavaScript engine to=
 mitigate the various issues we have with SpiderMonkey.
> This ticket acts as the meta-issue where we can discuss whether we all ag=
ree and what needs doing. individual tasks then can get their own tickets.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira