> > If it looks anything like web frameworks look right now, there is a > >> defacto winner and some strong 2nd and 3rd place competitors with decent >> communities behind them. >> > > I think they are quite different environments though; view engines are > heavily constrained by couch itself, so different python implementations are > likely to differ by not much more than the spelling or other "semantic > sugar" type distinctions. I think this is the reason why alternative JS > implementations haven't evolved - the requirements are so tightly > constrained that alternative implementations really have no way of providing > compelling advantages. People want the ability to use different engines for > entirely pragmatic reasons, but they aren't calling for a different API.
> I just don't understand why I would *want* to choose between the 2. Unlike > web-frameworks, I can't see how the two could offer APIs so different that > only 1 is suited to some kind of task, while the other is suited to some > other kind of task. IOW, I don't see how they could differ in ways > meaningful enough to make the choice valuable. Just like for Javascript. > CouchDB is taking on the role of an application server. While each call to the view server lives inside certain constraints there is still a lot of differing opinions about how to write the application logic in a web server. -Mikeal
