You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Robert Newson <ro...@gmail.com> on 2012/10/09 16:03:40 UTC
Re: Inspiring comment about CouchDB on Hacker News
I'll be in Boston next week and plan to spend a good chunk of time
with davisp on the merge. If not actually doing it, since we'd have to
do over, but a trial run through.
For 1.3, I think it's just CORS patch waiting now? No movement in a
while so I wonder if we can agree that if we don't make progress by
the end of this month, we bump it to 1.4. As for couchdb-1175, the
conneg thing, I suggest we bump that to Future or close it. Since we
plan regular time-based releases, bumping should be a normal operation
anyway.
There must be some more minor and not so minor bugs we could fix in
1.3 that are not marked for the release and possibly not even filed. I
encourage everyone to look for those things and tag them for 1.3. A
flurry of small fixes would be great, giving us the foundation for the
merge. I will separately look for any fixes that cloudant have made to
our couchdb code with a view to back porting. I know we have some
important fixes and enhancements to the new 1.2 replicator. Anyone,
dev or user, that spends time finding and filing replicator related
tickets for 1.3 is making a meaningful contribution.
Sent from the ocean floor
On 9 Oct 2012, at 13:47, Noah Slater <ns...@tumbolia.org> wrote:
> I wouldn't worry too much about that. Perhaps he has no experience of
> BigCouch, and only saw the lack of conversation about it. But overall, I
> like his vision. Of course I would. I don't necessarily believe that there
> is a "race" to "win", but I do think we're doing ourselves favours by not
> bending to the whim of the masses, and competing on features. Trying to
> please everyone is the quickest route to mediocrity. However, we could
> probably pick up our pace a little bit. And after the 1.3 release, I'm
> hoping we can pitch together as a group, and do a bit of community/release
> management.
>
> On Tue, Oct 9, 2012 at 12:43 PM, Robert Newson <ro...@gmail.com>wrote:
>
>> That "defunct" comment is rather upsetting. Wasn't true then, isn't
>> true now. But perhaps this just reinforces my zero tolerance policy on
>> HN.
>>
>> Sent from the ocean floor
>>
>> On 9 Oct 2012, at 10:50, Noah Slater <ns...@tumbolia.org> wrote:
>>
>>> My old CouchDB retrospective ended up on the front page of HN, again...
>>>
>>> http://hackerne.ws/item?id=4622986
>>>
>>> I thought I would quote this, by Riyad Kalla, because I find it very
>>> inspiring:
>>>
>>> FWIW, this was written in July of 2010 (2+ years ago) -- CouchDB is in a
>>>> very different place now than it was then.
>>>
>>>
>>>
>>> Reading the mailing lists of CouchDB, Redis, MongoDB and Cassandra are
>>>> _very_ different experiences.
>>>
>>>
>>>
>>> CouchDB's list reads like 10 or so of the same people discussing very
>> high
>>>> level efforts like documentation and Windows builds, developing the DB
>> at a
>>>> glacial pace -- including merging in changes from all the spin-off
>> CouchDB
>>>> efforts that all seem to be defunct now (e.g. BigCouch and the sharding
>>>> code).
>>>
>>>
>>>
>>> Tangentially, MongoDB/Redis/Cassandra mailing lists are NOTHING but "How
>> do
>>>> I..." questions, deployment questions, feature development questions,
>> patch
>>>> submissions, etc. (more-so Cassandra and MongoDB lists).
>>>
>>>
>>>
>>> CouchDB to me has found this life that feels very academic to me which I
>>>> think is a good thing in the long-term for the project. The principles
>> are
>>>> in no rush to get to features and have the motto "slow and consistent
>> wins
>>>> the race". I would be surprised at all if a few years go by and then
>>>> CouchDB gets rediscovered suddenly as the panacea to everything
>> (something
>>>> akin to how Jetty suddenly became hot business in the Java server world
>>>> after being mostly ignored for 10 years)
>>>
>>>
>>>
>>> With the money behind Cassandra and Mongo it is probably not much of a
>>>> surprise that there are much more new deployments going on and Redis has
>>>> found a place somewhere between the two with what I would say is a
>>>> Linus-like steward at the helm (props to Salvatorefor being everything
>> that
>>>> is right with open-source)
>>>
>>>
>>>
>>> I wouldn't build a commercial product on CouchDB tomorrow, but I am
>> eagerly
>>>> waiting to see where it goes in the next year. It is wonderfully
>> designed,
>>>> but I'd like to see some of the nagging "table stakes" issues like
>>>> replication failures fixed before caring about Feature XYZ and release
>> 2.0
>>>
>>>
>>> Here's to the future! We have a lot of work to do.
>>>
>>> Bisou,
>>>
>>> --
>>> NS
>
>
>
> --
> NS
Re: Inspiring comment about CouchDB on Hacker News
Posted by svilen <az...@svilendobrev.com>.
sorry to chime in, i dont know why's it about "win" and "race" (is it
just looking for intrigues and keywords), but this thing -
couchdb + mass_replication - *can* replace e-mail (think IMAP). And put
"state" back into protocol/API-messaging. (eh, with proper
setup/code above it). Thus open doors to much more productive
intra-device/people communication.
keep up the good work!
and have fun
svil
On Tue, 9 Oct 2012 15:03:40 +0100
Robert Newson <ro...@gmail.com> wrote:
> I'll be in Boston next week and plan to spend a good chunk of time
> with davisp on the merge. If not actually doing it, since we'd have to
> do over, but a trial run through.
>
> For 1.3, I think it's just CORS patch waiting now? No movement in a
> while so I wonder if we can agree that if we don't make progress by
> the end of this month, we bump it to 1.4. As for couchdb-1175, the
> conneg thing, I suggest we bump that to Future or close it. Since we
> plan regular time-based releases, bumping should be a normal operation
> anyway.
>
> There must be some more minor and not so minor bugs we could fix in
> 1.3 that are not marked for the release and possibly not even filed. I
> encourage everyone to look for those things and tag them for 1.3. A
> flurry of small fixes would be great, giving us the foundation for the
> merge. I will separately look for any fixes that cloudant have made to
> our couchdb code with a view to back porting. I know we have some
> important fixes and enhancements to the new 1.2 replicator. Anyone,
> dev or user, that spends time finding and filing replicator related
> tickets for 1.3 is making a meaningful contribution.
>
> Sent from the ocean floor
>
> On 9 Oct 2012, at 13:47, Noah Slater <ns...@tumbolia.org> wrote:
>
> > I wouldn't worry too much about that. Perhaps he has no experience
> > of BigCouch, and only saw the lack of conversation about it. But
> > overall, I like his vision. Of course I would. I don't necessarily
> > believe that there is a "race" to "win", but I do think we're doing
> > ourselves favours by not bending to the whim of the masses, and
> > competing on features. Trying to please everyone is the quickest
> > route to mediocrity. However, we could probably pick up our pace a
> > little bit. And after the 1.3 release, I'm hoping we can pitch
> > together as a group, and do a bit of community/release management.
> >
> > On Tue, Oct 9, 2012 at 12:43 PM, Robert Newson
> > <ro...@gmail.com>wrote:
> >
> >> That "defunct" comment is rather upsetting. Wasn't true then, isn't
> >> true now. But perhaps this just reinforces my zero tolerance
> >> policy on HN.
> >>
> >> Sent from the ocean floor
> >>
> >> On 9 Oct 2012, at 10:50, Noah Slater <ns...@tumbolia.org> wrote:
> >>
> >>> My old CouchDB retrospective ended up on the front page of HN,
> >>> again...
> >>>
> >>> http://hackerne.ws/item?id=4622986
> >>>
> >>> I thought I would quote this, by Riyad Kalla, because I find it
> >>> very inspiring:
> >>>
> >>> FWIW, this was written in July of 2010 (2+ years ago) -- CouchDB
> >>> is in a
> >>>> very different place now than it was then.
> >>>
> >>>
Re: Inspiring comment about CouchDB on Hacker News
Posted by Noah Slater <ns...@tumbolia.org>.
+1 for master and +1 for branches in future. (Though we have said this
before. Let's mean it this time!)
On Tue, Oct 9, 2012 at 8:06 PM, Dave Cottlehuber <dc...@jsonified.com> wrote:
> On 9 October 2012 19:08, Benoit Chesneau <bc...@gmail.com> wrote:
> > On Tue, Oct 9, 2012 at 6:54 PM, Robert Newson <ro...@gmail.com>
> wrote:
> >> Haven't thought deeply about it, I just know that cloudant and
> >> iriscouch customers will need separate controls. Ideally, we can all
> >> use the same code without forking. Maybe it's a special thing like
> >> _security, dunno. Lets puzzle it once the patch lands?
> >
> > yup :)
> >
> > - benoît
>
> Great news Benoît!
>
> +1 for CORS going direct into master. This will be by far the fastest
> way to get it out to people who are keen to test & I think we don't
> have other code/functionality landing that will conflict it. It's also
> a great opportunity to add this to the documentation :)
>
> Re COUCHDB-1346 Adam Lofts has put a related patch up on github as a
> pull req, I hope to look at that later this week when I have a windows
> VM available again.
>
> A+
> Dave
>
--
NS
Re: Inspiring comment about CouchDB on Hacker News
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 9 October 2012 19:08, Benoit Chesneau <bc...@gmail.com> wrote:
> On Tue, Oct 9, 2012 at 6:54 PM, Robert Newson <ro...@gmail.com> wrote:
>> Haven't thought deeply about it, I just know that cloudant and
>> iriscouch customers will need separate controls. Ideally, we can all
>> use the same code without forking. Maybe it's a special thing like
>> _security, dunno. Lets puzzle it once the patch lands?
>
> yup :)
>
> - benoît
Great news Benoît!
+1 for CORS going direct into master. This will be by far the fastest
way to get it out to people who are keen to test & I think we don't
have other code/functionality landing that will conflict it. It's also
a great opportunity to add this to the documentation :)
Re COUCHDB-1346 Adam Lofts has put a related patch up on github as a
pull req, I hope to look at that later this week when I have a windows
VM available again.
A+
Dave
Re: Inspiring comment about CouchDB on Hacker News
Posted by Benoit Chesneau <bc...@gmail.com>.
On Tue, Oct 9, 2012 at 6:54 PM, Robert Newson <ro...@gmail.com> wrote:
> Haven't thought deeply about it, I just know that cloudant and
> iriscouch customers will need separate controls. Ideally, we can all
> use the same code without forking. Maybe it's a special thing like
> _security, dunno. Lets puzzle it once the patch lands?
yup :)
- benoît
Re: Inspiring comment about CouchDB on Hacker News
Posted by Robert Newson <ro...@gmail.com>.
Haven't thought deeply about it, I just know that cloudant and
iriscouch customers will need separate controls. Ideally, we can all
use the same code without forking. Maybe it's a special thing like
_security, dunno. Lets puzzle it once the patch lands?
Sent from the ocean floor
On 9 Oct 2012, at 16:42, Benoit Chesneau <bc...@gmail.com> wrote:
> On Tue, Oct 9, 2012 at 5:38 PM, Robert Newson <ro...@gmail.com> wrote:
>> Since ini config is not available to users on cloudant (and
>> iriscouch?), a ddoc seems more appropriate, but happy to defer until
>> the first patch lands where we can all play.
>
> mmm for a thing I put the conf in a doozer cluster, so i guess it can
> be changed quite easily. I'm not sure how it would work in a design
> document. What do you have in mind?
>
> - benoît
Re: Inspiring comment about CouchDB on Hacker News
Posted by Benoit Chesneau <bc...@gmail.com>.
On Tue, Oct 9, 2012 at 5:38 PM, Robert Newson <ro...@gmail.com> wrote:
> Since ini config is not available to users on cloudant (and
> iriscouch?), a ddoc seems more appropriate, but happy to defer until
> the first patch lands where we can all play.
mmm for a thing I put the conf in a doozer cluster, so i guess it can
be changed quite easily. I'm not sure how it would work in a design
document. What do you have in mind?
- benoît
Re: Inspiring comment about CouchDB on Hacker News
Posted by Robert Newson <ro...@gmail.com>.
Since ini config is not available to users on cloudant (and
iriscouch?), a ddoc seems more appropriate, but happy to defer until
the first patch lands where we can all play.
Sent from the ocean floor
On 9 Oct 2012, at 16:35, Benoit Chesneau <bc...@gmail.com> wrote:
> On Tue, Oct 9, 2012 at 5:08 PM, Aurélien Bénel <au...@utt.fr> wrote:
>>> CORS is quite ready.
>>
>> Cool :)
>>
>> I'm curious though. How will it be setup in CouchDB?
>> Will the authorized sites list be defined in the server settings?
>> Or in design documents? With which granularity (URLs, methods)?
>
> config / couchdb node in the ini , methods & co will be configurable.
Re: Inspiring comment about CouchDB on Hacker News
Posted by Benoit Chesneau <bc...@gmail.com>.
On Tue, Oct 9, 2012 at 5:08 PM, Aurélien Bénel <au...@utt.fr> wrote:
>> CORS is quite ready.
>
> Cool :)
>
> I'm curious though. How will it be setup in CouchDB?
> Will the authorized sites list be defined in the server settings?
> Or in design documents? With which granularity (URLs, methods)?
>
>
config / couchdb node in the ini , methods & co will be configurable.
Re: Inspiring comment about CouchDB on Hacker News
Posted by Aurélien Bénel <au...@utt.fr>.
> CORS is quite ready.
Cool :)
I'm curious though. How will it be setup in CouchDB?
Will the authorized sites list be defined in the server settings?
Or in design documents? With which granularity (URLs, methods)?
Regards,
Aurélien
Re: Inspiring comment about CouchDB on Hacker News
Posted by Robert Newson <ro...@gmail.com>.
I hear you and I agree that having the merge happen out of sight is
not the way. It won't be that way, of course. The initial stuff is
fiddly but boring, which is why davisp and I are taking it on. I think
a merge branch will land in our asf repo in a reasonable but
unfinished state. At that point everyone will need to get involved. We
have pending discussions on api changes too (couchdb still has a few
warts when clustered like all_or_nothing, etc). Some of those will be
implemented, others will, rightly, be removed for good. We also will
want to look at perf regressions for single node clusters. The bc
merge itself is the beginning, not the end, of this work.
Great news on CORS. I knew you had a patch but I didn't see it land in
master or get many eyeballs yet. How does everyone feel about having
it land directly into master and have it tested there? Future releases
will be strictly feature branches and merges, but I'd be ok with an
exception here to get this long overdue feature.
Sent from the ocean floor
On 9 Oct 2012, at 15:59, Benoit Chesneau <bc...@gmail.com> wrote:
> On Tue, Oct 9, 2012 at 4:03 PM, Robert Newson <ro...@gmail.com> wrote:
>> I'll be in Boston next week and plan to spend a good chunk of time
>> with davisp on the merge. If not actually doing it, since we'd have to
>> do over, but a trial run through.
>
> Would be cool to share the plan in between or during imo. So we can be
> proactive instead of beein reactive :) But sounds really good.
>>
>> For 1.3, I think it's just CORS patch waiting now? No movement in a
>> while so I wonder if we can agree that if we don't make progress by
>> the end of this month, we bump it to 1.4. As for couchdb-1175, the
>> conneg thing, I suggest we bump that to Future or close it. Since we
>> plan regular time-based releases, bumping should be a normal operation
>> anyway.
> Cors is quite ready. I am actually busy on the refuge beta released on
> friday for a pitcj. CORS pach is included. I will releasing on
> thursday as a branch, waiting that I am mostly offline playing with
> the code, feel free to ping me over irc if you have any questions.
>
>
> - benoit
Re: Inspiring comment about CouchDB on Hacker News
Posted by Benoit Chesneau <bc...@gmail.com>.
On Tue, Oct 9, 2012 at 4:03 PM, Robert Newson <ro...@gmail.com> wrote:
> I'll be in Boston next week and plan to spend a good chunk of time
> with davisp on the merge. If not actually doing it, since we'd have to
> do over, but a trial run through.
Would be cool to share the plan in between or during imo. So we can be
proactive instead of beein reactive :) But sounds really good.
>
> For 1.3, I think it's just CORS patch waiting now? No movement in a
> while so I wonder if we can agree that if we don't make progress by
> the end of this month, we bump it to 1.4. As for couchdb-1175, the
> conneg thing, I suggest we bump that to Future or close it. Since we
> plan regular time-based releases, bumping should be a normal operation
> anyway.
>
Cors is quite ready. I am actually busy on the refuge beta released on
friday for a pitcj. CORS pach is included. I will releasing on
thursday as a branch, waiting that I am mostly offline playing with
the code, feel free to ping me over irc if you have any questions.
- benoit
Re: Inspiring comment about CouchDB on Hacker News
Posted by Noah Slater <ns...@tumbolia.org>.
+1 on everything Bob says.
On Tue, Oct 9, 2012 at 3:03 PM, Robert Newson <ro...@gmail.com>wrote:
> I'll be in Boston next week and plan to spend a good chunk of time
> with davisp on the merge. If not actually doing it, since we'd have to
> do over, but a trial run through.
>
> For 1.3, I think it's just CORS patch waiting now? No movement in a
> while so I wonder if we can agree that if we don't make progress by
> the end of this month, we bump it to 1.4. As for couchdb-1175, the
> conneg thing, I suggest we bump that to Future or close it. Since we
> plan regular time-based releases, bumping should be a normal operation
> anyway.
>
> There must be some more minor and not so minor bugs we could fix in
> 1.3 that are not marked for the release and possibly not even filed. I
> encourage everyone to look for those things and tag them for 1.3. A
> flurry of small fixes would be great, giving us the foundation for the
> merge. I will separately look for any fixes that cloudant have made to
> our couchdb code with a view to back porting. I know we have some
> important fixes and enhancements to the new 1.2 replicator. Anyone,
> dev or user, that spends time finding and filing replicator related
> tickets for 1.3 is making a meaningful contribution.
>
> Sent from the ocean floor
>
> On 9 Oct 2012, at 13:47, Noah Slater <ns...@tumbolia.org> wrote:
>
> > I wouldn't worry too much about that. Perhaps he has no experience of
> > BigCouch, and only saw the lack of conversation about it. But overall, I
> > like his vision. Of course I would. I don't necessarily believe that
> there
> > is a "race" to "win", but I do think we're doing ourselves favours by not
> > bending to the whim of the masses, and competing on features. Trying to
> > please everyone is the quickest route to mediocrity. However, we could
> > probably pick up our pace a little bit. And after the 1.3 release, I'm
> > hoping we can pitch together as a group, and do a bit of
> community/release
> > management.
> >
> > On Tue, Oct 9, 2012 at 12:43 PM, Robert Newson <robert.newson@gmail.com
> >wrote:
> >
> >> That "defunct" comment is rather upsetting. Wasn't true then, isn't
> >> true now. But perhaps this just reinforces my zero tolerance policy on
> >> HN.
> >>
> >> Sent from the ocean floor
> >>
> >> On 9 Oct 2012, at 10:50, Noah Slater <ns...@tumbolia.org> wrote:
> >>
> >>> My old CouchDB retrospective ended up on the front page of HN, again...
> >>>
> >>> http://hackerne.ws/item?id=4622986
> >>>
> >>> I thought I would quote this, by Riyad Kalla, because I find it very
> >>> inspiring:
> >>>
> >>> FWIW, this was written in July of 2010 (2+ years ago) -- CouchDB is in
> a
> >>>> very different place now than it was then.
> >>>
> >>>
> >>>
> >>> Reading the mailing lists of CouchDB, Redis, MongoDB and Cassandra are
> >>>> _very_ different experiences.
> >>>
> >>>
> >>>
> >>> CouchDB's list reads like 10 or so of the same people discussing very
> >> high
> >>>> level efforts like documentation and Windows builds, developing the DB
> >> at a
> >>>> glacial pace -- including merging in changes from all the spin-off
> >> CouchDB
> >>>> efforts that all seem to be defunct now (e.g. BigCouch and the
> sharding
> >>>> code).
> >>>
> >>>
> >>>
> >>> Tangentially, MongoDB/Redis/Cassandra mailing lists are NOTHING but
> "How
> >> do
> >>>> I..." questions, deployment questions, feature development questions,
> >> patch
> >>>> submissions, etc. (more-so Cassandra and MongoDB lists).
> >>>
> >>>
> >>>
> >>> CouchDB to me has found this life that feels very academic to me which
> I
> >>>> think is a good thing in the long-term for the project. The principles
> >> are
> >>>> in no rush to get to features and have the motto "slow and consistent
> >> wins
> >>>> the race". I would be surprised at all if a few years go by and then
> >>>> CouchDB gets rediscovered suddenly as the panacea to everything
> >> (something
> >>>> akin to how Jetty suddenly became hot business in the Java server
> world
> >>>> after being mostly ignored for 10 years)
> >>>
> >>>
> >>>
> >>> With the money behind Cassandra and Mongo it is probably not much of a
> >>>> surprise that there are much more new deployments going on and Redis
> has
> >>>> found a place somewhere between the two with what I would say is a
> >>>> Linus-like steward at the helm (props to Salvatorefor being everything
> >> that
> >>>> is right with open-source)
> >>>
> >>>
> >>>
> >>> I wouldn't build a commercial product on CouchDB tomorrow, but I am
> >> eagerly
> >>>> waiting to see where it goes in the next year. It is wonderfully
> >> designed,
> >>>> but I'd like to see some of the nagging "table stakes" issues like
> >>>> replication failures fixed before caring about Feature XYZ and release
> >> 2.0
> >>>
> >>>
> >>> Here's to the future! We have a lot of work to do.
> >>>
> >>> Bisou,
> >>>
> >>> --
> >>> NS
> >
> >
> >
> > --
> > NS
>
--
NS
Re: Inspiring comment about CouchDB on Hacker News
Posted by Noah Slater <ns...@tumbolia.org>.
+1 on everything Bob says.
On Tue, Oct 9, 2012 at 3:03 PM, Robert Newson <ro...@gmail.com>wrote:
> I'll be in Boston next week and plan to spend a good chunk of time
> with davisp on the merge. If not actually doing it, since we'd have to
> do over, but a trial run through.
>
> For 1.3, I think it's just CORS patch waiting now? No movement in a
> while so I wonder if we can agree that if we don't make progress by
> the end of this month, we bump it to 1.4. As for couchdb-1175, the
> conneg thing, I suggest we bump that to Future or close it. Since we
> plan regular time-based releases, bumping should be a normal operation
> anyway.
>
> There must be some more minor and not so minor bugs we could fix in
> 1.3 that are not marked for the release and possibly not even filed. I
> encourage everyone to look for those things and tag them for 1.3. A
> flurry of small fixes would be great, giving us the foundation for the
> merge. I will separately look for any fixes that cloudant have made to
> our couchdb code with a view to back porting. I know we have some
> important fixes and enhancements to the new 1.2 replicator. Anyone,
> dev or user, that spends time finding and filing replicator related
> tickets for 1.3 is making a meaningful contribution.
>
> Sent from the ocean floor
>
> On 9 Oct 2012, at 13:47, Noah Slater <ns...@tumbolia.org> wrote:
>
> > I wouldn't worry too much about that. Perhaps he has no experience of
> > BigCouch, and only saw the lack of conversation about it. But overall, I
> > like his vision. Of course I would. I don't necessarily believe that
> there
> > is a "race" to "win", but I do think we're doing ourselves favours by not
> > bending to the whim of the masses, and competing on features. Trying to
> > please everyone is the quickest route to mediocrity. However, we could
> > probably pick up our pace a little bit. And after the 1.3 release, I'm
> > hoping we can pitch together as a group, and do a bit of
> community/release
> > management.
> >
> > On Tue, Oct 9, 2012 at 12:43 PM, Robert Newson <robert.newson@gmail.com
> >wrote:
> >
> >> That "defunct" comment is rather upsetting. Wasn't true then, isn't
> >> true now. But perhaps this just reinforces my zero tolerance policy on
> >> HN.
> >>
> >> Sent from the ocean floor
> >>
> >> On 9 Oct 2012, at 10:50, Noah Slater <ns...@tumbolia.org> wrote:
> >>
> >>> My old CouchDB retrospective ended up on the front page of HN, again...
> >>>
> >>> http://hackerne.ws/item?id=4622986
> >>>
> >>> I thought I would quote this, by Riyad Kalla, because I find it very
> >>> inspiring:
> >>>
> >>> FWIW, this was written in July of 2010 (2+ years ago) -- CouchDB is in
> a
> >>>> very different place now than it was then.
> >>>
> >>>
> >>>
> >>> Reading the mailing lists of CouchDB, Redis, MongoDB and Cassandra are
> >>>> _very_ different experiences.
> >>>
> >>>
> >>>
> >>> CouchDB's list reads like 10 or so of the same people discussing very
> >> high
> >>>> level efforts like documentation and Windows builds, developing the DB
> >> at a
> >>>> glacial pace -- including merging in changes from all the spin-off
> >> CouchDB
> >>>> efforts that all seem to be defunct now (e.g. BigCouch and the
> sharding
> >>>> code).
> >>>
> >>>
> >>>
> >>> Tangentially, MongoDB/Redis/Cassandra mailing lists are NOTHING but
> "How
> >> do
> >>>> I..." questions, deployment questions, feature development questions,
> >> patch
> >>>> submissions, etc. (more-so Cassandra and MongoDB lists).
> >>>
> >>>
> >>>
> >>> CouchDB to me has found this life that feels very academic to me which
> I
> >>>> think is a good thing in the long-term for the project. The principles
> >> are
> >>>> in no rush to get to features and have the motto "slow and consistent
> >> wins
> >>>> the race". I would be surprised at all if a few years go by and then
> >>>> CouchDB gets rediscovered suddenly as the panacea to everything
> >> (something
> >>>> akin to how Jetty suddenly became hot business in the Java server
> world
> >>>> after being mostly ignored for 10 years)
> >>>
> >>>
> >>>
> >>> With the money behind Cassandra and Mongo it is probably not much of a
> >>>> surprise that there are much more new deployments going on and Redis
> has
> >>>> found a place somewhere between the two with what I would say is a
> >>>> Linus-like steward at the helm (props to Salvatorefor being everything
> >> that
> >>>> is right with open-source)
> >>>
> >>>
> >>>
> >>> I wouldn't build a commercial product on CouchDB tomorrow, but I am
> >> eagerly
> >>>> waiting to see where it goes in the next year. It is wonderfully
> >> designed,
> >>>> but I'd like to see some of the nagging "table stakes" issues like
> >>>> replication failures fixed before caring about Feature XYZ and release
> >> 2.0
> >>>
> >>>
> >>> Here's to the future! We have a lot of work to do.
> >>>
> >>> Bisou,
> >>>
> >>> --
> >>> NS
> >
> >
> >
> > --
> > NS
>
--
NS