I am a data scientist. When I needed to learn how to build a web application, Couchapp was the first thing I learned. I chose it because it was the only thing I could really understand. Viewed as a system, it's a lot simpler to have one thing storing your application code and data, instead of two or more things which must communicate with each other. After my first few apps, I learned to use Backbone, d3, etc. in my Couchapps. I find the results better than what I can get creating an R-Shiny or Flask application. In summary, the Couchapp architecture makes it easier to get started programming web applications, without having to learn some middleman API.
On Fri, Sep 2, 2016 at 12:14 AM, Martin Broerse <martin.broe...@gmail.com> wrote: > > > > deep CouchDB understanding and experience > > > You need tooling but without deep understanding you can deploy an Ember > application as couchapp. See: > https://www.npmjs.com/package/ember-cli-deploy-couchdb > Working example: https://github.com/broerse/ember-cli-blog > > - Martin > > > On Fri, Sep 2, 2016 at 12:00 AM, ermouth <ermo...@gmail.com> wrote: > > > Tried out more or less pure couchapp approach in 2016 realities, I mean > JS > > rewrites and PouchDB. > > > > Written down a story about the project, from the couchapp side: > > http://lesorub.pro/how-it-works > > > > It was interesting experience, couchapps still might be useful, in very > > rare cases ) > > > > ermouth > > >
