couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Ramage <>
Subject Re: Part2: What's up dev? About couchapps.
Date Tue, 25 Sep 2012 14:01:40 GMT
On Tue, Sep 25, 2012 at 5:52 AM, Dirkjan Ochtman <> wrote:

> organized around CouchApps. I think that currently, the swirling
> vortex of CouchApp-like projects is more of a distraction to the
> CouchDB community than a force for constructive feedback.

Yes, couchapps can be criticized for being very distracting. I have
been told that they are especially confusing for newcomers. I get it,
its been a while since I have been there, but yes I can remember that

On the flip side though, the design of couchdb leads itself to
'couchapps'. It is built around design docs, which are 'couchapps'
themselves. One needs to push design docs to couchdb. So in that sense
they are actually at the heart of couchdb. There is a trasformation
from outside couch into couch. This process is the kernel of a

This leads to the fallacy of the simple couchapp tool.
(tomorrow is "international wheel reinvention day". go rewrite

It starts with, "Getting stuff into couch is so simple over http" and
"I love my language 'x' and my way of doing things 'z' in that
language. I am just going to write something quick and tell all my
friends about it." You have just killed one puppy and a newbie. The
community has been fractured. Your post telling your friends lives on
3 yrs down the road, and for some reason people still stumble in it. I
have been there, I have fallen to the same sin. Obviously we are not
the only community that suffers it.

So understanding the root of the couchapp is the key to the
discussion. It has arisen to solve two problems. 1. To 'push' or
'sync' stuff into design docs, and 2. as a general purpose build tool
(or a transformation tool).

I was going to go into this more, but I will in another email as I am
trying to catch up to the emails flying in as I write this...


View raw message