Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jan.wedekind@gmail.com
 designates 209.85.210.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAN-3CBLog0VMXZYN622+3ZN=_JV09fi1UTW54rFR=-3nP6+sVQ@mail.gmail.com>
References: 
 <CA+5KyPSE3BULUc7KONgx8ZqfNKW++_r8vgdhh7HLxLr0JgfM0A@mail.gmail.com>
 <CAONf+LQKjE6NVCsLKWb3wzmWOwrS2ej+_PCJS4Z=uV3hj0OtOg@mail.gmail.com>
 <CAOHkvcP0XMAFvvFhaw3azEyqBxPMhNxFwkYX+5_x52ScSaxEbg@mail.gmail.com>
 <CAMkGvyNO4GC8e+PWu8u7BpV6b4OUvXZ3v37y5kpnXdrYgn_nBA@mail.gmail.com>
 <4E371B93.8060303@kearns.net.au>
 <CAAL6JQj_u0RgDhQG95oFrQfJ3MUeRXHb+Q6d1Cc6DEBUwaE_vA@mail.gmail.com>
 <CAONf+LTt0Hmuhx8PTs_LdzzX-fHQDAhQg_kJabTQAnfnBdxZqQ@mail.gmail.com>
 <CAOHkvcNutCimOggckR3ivc2=DCAP1ZhPTC2XpnP1o_E82_Pvaw@mail.gmail.com>
 <CA+5KyPR56FpKXiQ6Zyxu0V2jwaKbOghbTZyJ10Ou=YXyyk6zhA@mail.gmail.com>
 <CAONf+LTd+qQtLBb7iXb-H_HJs4Xm+t+Bw0G4CMLCC8X=bYwdFQ@mail.gmail.com>
 <CAAL6JQhytD90Jn3f7LT-HUMVH=T5GgTEMXWzaR6kQ5BgqZGRSw@mail.gmail.com>
 <CAAL6JQjbpOD9GOu-dDDf7-1-44pANT3U=ZKaNYEBXPcX11C8pA@mail.gmail.com>
 <CAN-3CBLheiAds-L5Vps-amEHN-F-17yRqHzbzNzAq-Ev9BKa5g@mail.gmail.com>
 <CAMWZAjnE9p2QB7zujjGqL-JiLMnbbimmuz3V-f+pW_bNeL4hng@mail.gmail.com>
 <CAN-3CBLog0VMXZYN622+3ZN=_JV09fi1UTW54rFR=-3nP6+sVQ@mail.gmail.com>
From: Jan Wedekind <jan.wedekind@gmail.com>
Date: Tue, 16 Aug 2011 13:30:09 +0200
Message-ID: 
 <CALnFx5q6J+a9C=O4ChadB+eKd115biK8wF5xc88T7uqHrgMHwA@mail.gmail.com>
Subject: Re: to CouchApp or not to CouchApp
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=00151774155af0f62304aa9db443

--00151774155af0f62304aa9db443
Content-Type: text/plain; charset=ISO-8859-1

Hi

On Tue, Aug 16, 2011 at 12:21, Jason Smith <jhs@iriscouch.com> wrote:

> It's time to ask whether the word "couchapp" does more harm than good.
> As a historical phenomenon, it is brilliant! The command-line tool is
> brilliant. But the word is meaningless. It is incoherent. It
> disappoints developers, setting expectations and then betraying them.
>

I think you're hitting the nail on the head. It's a brilliant concept but in
reality you run into so many open issues that it can lead to disappointment.
That's probably a bit unfair, but true.

Most of that can - and I am sure will be - resolved in time by better and
less scattered documentation. Right now, it's a often mess to find stuff.
Things are all over the place and often out-dated. Try googling for "couchdb
security"...

We all need
> welcome_mat, so it is worth building. This is HTTP. This is web
> development. Bringing an idea to completion, nothing ever works
> correctly anyway. That is the platform. Nothing ever works as planned.
> It's one disappointment after another. But, if you can work through
> the bugs, you've got an app on the most successful software platform
> ever (the web), and IMO the most visionary web platform ever
> (CouchDB). So I think it's worth it.
>

Me too! Totally worth it! :)

I think the book and wiki could definitely use a couple of real world
examples that take security into account. It obviously influences how you
have to distribute your data, what limitations/workarounds you need to live
with or implement etc.

Jan

--00151774155af0f62304aa9db443--