[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Shorin reopened COUCHDB-1934:
---------------------------------------
Hm, seems like I was in rush when closed the issue, getting it back.
> My -1 on the mailing list was conditional on hearing "no good reasons to
> remove it".
Sorry, seems like I miss them. In my pro/con list there is the next:
Reasons to keep it:
- Compatibility with existed couchapps // yes, I know how this sounds like, but
still
- Good bootstrap platform for new couchapps (especially with Fauxton assets and
libs)
- There is no alternative out of box remains, unless you'll hack through
Fauxton api
- CouchDB is "A Database for the Web" (as our site says) and with
client-out-of-the-box it would be just more awesome
Reasons to remove it:
- Not been actively maintaining
- The main reason why it was out-of-box was Futon
- And it remains unused in post-Futon era
- It's quite complex project that may evolve as standalone one
- Yet another point to keep compatibility with the rest of the world (if we're
changing HTTP API we SHOULD change jquery.couch too)
- If you cares about your couchapp portablity, you will not use builtin js
libs, but your own which you ship in attachments since this safes you from
compatibility/availability issues.
Anything else?
> plus issues with having them assumed to be available, couch instances that
> disable futon shouldnt suddenly break applications based on couch because of
> a broken dependancy
Good point. That is the main reason to have it in ddoc attachments since in
this case you would be saved from disabled futon and different versions issues.
> jquery.couch status
> -------------------
>
> Key: COUCHDB-1934
> URL: https://issues.apache.org/jira/browse/COUCHDB-1934
> Project: CouchDB
> Issue Type: Question
> Reporter: Alexander Shorin
>
> When [~nslater] had proposed to include [jquery.couch.js
> docs|http://daleharvey.github.io/jquery.couch.js-docs/symbols/] into official
> CouchDB one I recall old good time when we had discussed Futon.Next project.
> Suddenly, it was out of official mailing lists, so no references are
> available, but [~garren], [~dch], [~bigbluehat] and [~ryanramage] were there
> and our discussion was around jquery vs backbone vs pouchdb. Backbone won.
> Nowdays, we have Fauxton which doesn't used jquery.couch and based on
> Backbone. So it seems if we'll replace Futon with him this client library
> would be left orphan.
> So that's the question: what is the status of jquery.couch.js? Is it still
> actual and supported or going to be deprecated?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
