couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Octavian Damiean (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1643) Switch to V8
Date Wed, 16 Jan 2013 09:16:16 GMT


Octavian Damiean commented on COUCHDB-1643:

I like the idea of switching to v8. I'm +1 on that one.

[~benoitc] Regarding sandboxes. That's a bit tricky. Technically, sandboxing is possible however
as the documentation of the VM  module describes[1] there are some caveats to it. You can
run into bugs on ccertain edge cases. We'd have to evaluate our exact needs and check the
open issues to make sure we don't run into a known one, however that wouldn't protect us from
running into an unknown issue obviously.

The next problem with that module is that it is marked as unstable (stability 2) which doesn't
make it better for us.

The rest of the API seems mostly stable judging by the stability indices given on each module.
Again we'd have to evaluate what exactly we'd need to judge how risky it would be to go for
it. Here is a list of stability indices[2] with an explanation.

> Switch to V8
> ------------
>                 Key: COUCHDB-1643
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: JavaScript View Server
>            Reporter: Jan Lehnardt
> I’d 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 agree 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 administrators
For more information on JIRA, see:

View raw message