Agreed. Not sure we should ship more than one "reference implementation."
And just to be clear, I think the primary goal of this effort, if somebody undertakes it, is to provide a tool that can bootstrap Futon during the install process. A secondary goal should be that we can talk about the tool in the docs, and give people a taste for CouchApps. And the best way to do that, IMO, is to provide a tool that is simple and focused enough to upload a dir into a design document. (Unless Futon needs anything more than that? My CouchApp experience is... Spotty. I have built a few, but I am no expert.) On Tue, Sep 25, 2012 at 9:26 AM, Dirkjan Ochtman <dirk...@ochtman.nl> wrote: > On Tue, Sep 25, 2012 at 10:16 AM, Simon Metson <si...@cloudant.com> wrote: > > I was thinking about this "reference implementation" this morning. I > think having a bunch, in multiple languages might not be a bad idea. So a > simplified erica, couchapp.py, the node.js couchapp tool etc could all be > there. That would make picking up and reusing in a 3rd party app easier > (since I'd just import/require the thing) and might help constrain the > functionality and scope down to something really minimal… > > Having a bunch sounds like a strong argument in favor of not shipping > them with Apache CouchDB. > > Cheers, > > Dirkjan > -- NS
