I agree! At least, assuming you are speaking frankly and not sarcastically.
This is a great moment in the CouchDB community. Lots of viewpoints. Lots of different experience and expertise. Lots of discussion, all of it civil and respectful. It was positive for me, I just flat-out changed my mind midway through, based on argumentation from the community. It feels bracing and exciting! On Sun, Aug 18, 2013 at 2:11 PM, Jim Klo <[email protected]> wrote: > FWIW: this thread has been the best holy war I've read in a long time. > > :-) > > On Aug 17, 2013, at 11:51 PM, "Alexander Shorin" <[email protected]> wrote: > > > On Sun, Aug 18, 2013 at 10:29 AM, Benoit Chesneau <[email protected]> > wrote: > >> On Sun, Aug 18, 2013 at 6:51 AM, Thanos Vassilakis <[email protected] > >wrote: > >> > >>> Build views performance gains: > >>> Python 4-6 times faster + less memory > >> > >> > >> Whatever the results of this benchmark are, this not the first time, I > >> heard that the python engine is faster than the Javascript one. I wonder > >> what could make it faster than the javascript engine. Since the protocol > >> and encode/decode steps are the same, this is likely an issue in the > >> couchjs program. That would be interesting to see where the JS engine > lost > >> times and eventually fix it. > > > > As for my experience, Python is not faster than JS until you don't > > have to use stdlib or other packages actively. Lack of stdlib power > > forces you write/ship a lot of routine code, that mostly not so fast > > and effective as some C-extension on disk "that does magic" for > > Python. For simple cases like > > > > def map(doc): > > if 'foo' in doc: > > yield doc['foo'], 1 > > > > you will not see the profit. > > > > -- > > ,,,^..^,,, >
