johs commented on issue #1534: proposed 1.x deprecations URL: https://github.com/apache/couchdb/issues/1534#issuecomment-412485492 We have never been closer to the core of the "couchapp" discussion than with @joan discussing differntiation in DB land: > I can't think of another database engine that allows you to rewrite its API.... .. and @giowild discussing _onboarding_ > If no app developers will ever write apps with couchdb, no db or system administrators will be ever required to mantain its databases! .. and @ermouth discussing _syncing_ code with data > I think most features using benefits of syncing code with data flow better be kept. .. not forgetting the _prototyping_ feature that @nolanlawson desicribed so well back in 2014: >ultimately your webapp will grow in complexity to the point where you’re forced to put a proxy server in front of CouchDB to smooth out its rougher edges, but I think you’ll still be amazed how far you can get with vanilla Couch. ### CouchDB has offered __truly unique__ CI/CD productivity on a single platform. If the work with the https://github.com/cloudant-labs/erlang-chakracore is successful and javascript developers can still host their server-side functions in CouchDB and clientside apps as attachements maintained in couch/pouch mini-IDEs like http://ddoc.me/ I think the most interesting question is: __What is the disadvantage of preserving the experimental space of design documents?__ If this opportunity space -- especially related to onboarding -- can be preserved at low cost, then it would be very unwise to remove it.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
