Couchapp 0.8 released

#1

Post by benoitc » Sun, May 08, 2011, 4:45 PM UTC

Re: Couchapp 0.8 released

#2

Post by Meai » Sun, May 08, 2011, 5:45 PM UTC

I like the minimalistic drive, but in the end it boils down to javascript on the serverside. Which you can agree with or not.

Re: Couchapp 0.8 released

#3

Post by benoitc » Sun, May 08, 2011, 6:26 PM UTC

Meai wrote: post #2

I like the minimalistic drive, but in the end it boils down to javascript on the serverside. Which you can agree with or not.

what would you want?

Re: Couchapp 0.8 released

#4

Post by Meai » Sun, May 08, 2011, 6:44 PM UTC

benoitc wrote: post #3

Meai wrote: post #2

I like the minimalistic drive, but in the end it boils down to javascript on the serverside. Which you can agree with or not.

what would you want?

I don't think CouchApp is a good choice for any target market. Most people eventually need to execute more arbitrary code on the serverside. Theoretically the Wordpress crowd would be a good target, but they don't like to code. You would need to aim for zero configuration. (it's fine, just know your market) Personally, I wouldn't feel safe to rely on CouchApp. What if my site goes viral and I need much more functionality? I'd have nothing to build up on, and I'd eventually need to rebuild on nodejs or something else.

Re: Couchapp 0.8 released

#5

Post by po » Sun, May 08, 2011, 7:50 PM UTC

What ever became of the erlang branch?

https://github.com/couchapp/couchapp/tree/erlang

I never really understood what the main driver behind that was. Are there still plans to release that?

Re: Couchapp 0.8 released

#6

Post by po » Sun, May 08, 2011, 7:57 PM UTC

Meai wrote: post #4

benoitc wrote: post #3

Earlier quoted context omitted.

what would you want?

I don't think CouchApp is a good choice for any target market. Most people eventually need to execute more arbitrary code on the serverside. Theoretically the Wordpress crowd would be a good target, but they don't like to code. You would need to aim for zero configuration. (it's fine, just know your market) Personally, I wouldn't feel safe to rely on CouchApp. What if my site goes viral and I need much more functiona…

A Couchapp has features that are trivial in couchdb (replication, map-reduce) but require more setup in traditional server side code. The target market will be applications that value these tradeoffs.

If you decide you need something else, I don't see the problem with having some parts of the application served by couchdb and some served by node. Put it behind varnish, cdn the static content, add a queueing system or whatever...

I think a couchapp is a decent way to prototype something out and if it goes viral you're going to be rewriting everything anyway no matter what system you use.