[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13834713#comment-13834713
]
Dale Harvey commented on COUCHDB-1934:
--------------------------------------
Having jquery.couch.js's canonical location inside CouchDB never made sense,
its a client library, a completely seperate project (and one that is extremely
dated one at that), People fixing a client library shouldnt have to deal with
the same intricacies that a db core developer has to worry about
Project organisation aside, there have been problems with jquery.couch forcing
limitations on the jquery version, 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
The proposal to deprecate it then remove along with a major version bump was a
good one, we shouldnt be scared to make positive changes to CouchDB just
because its effort to make them.
> 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)
