ermouth commented on issue #1534: proposed 1.x deprecations
   > recognize you are angry and want to fight for something you believe in
   > You want to contribute to couchapps still?
   There is kind of misunderstanding. We use couchapps, but not in the way you 
think. We have Couchbox, which completely replaces couchapp-related QS fns, 
able to run legacy code, and is much faster and reacher with features (but much 
heavier). So we do not need `_list`, `_rewrite` or `_update` for _couchapps_. 
   But there exist other scenarios, probably not so visible, where built-in QS 
stuff seem to be extremely valuable.
   Update fns is the only way to send whatever data to Couch without prior 
reading. It‘s invaluable feature for ie nets of sensors. Couch here acts as an 
aggregator, and ability to run Couch on PI allows to make aggregators very 
lean, setup them in place, and avoid app layer completely (which is obviously 
important for lean devices).
   Lists are also valuable for scenarios of aggregating data from net of 
sensors. You can perform remote data lookup on whatever basis without fetching 
real data, and have no serious bucket stalls, like you have with views. Mango 
queries seem to provide alternative mechanics for this, but they are less 
flexible (however much more fast).
   Rewrites (only as functions surely) are just great. Ability to re-wire API 
remotely has a lot of applications aside of couchapps. Also this approach of 
providing API is easily testable without deployment. Functions are easy to play 
with, unlike sets of nginx or haproxy rules.
   All those features just work. They might be faster, and some improvements 
are low hanging fruits, but they already work in acceptable way. They only need 
very minor repair time to time.
   So I can’t accept your ”submit PRs or stop complaining“. There’s not so lot 
of things I personally want to improve. However, I think I can help with fixing 
(or at least nailing down) QS-related bugs. Hope it may help to preserve those 
features little bit longer.

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:

With regards,
Apache Git Services

Reply via email to