Github user pmuellr commented on the pull request:
https://github.com/apache/cordova-lib/pull/305#issuecomment-139631229
@csantanapr re: not a fan of sync in node.js
Sync becomes a problem if you're wasting precious cycles in a single
operation, instead of using async to potentially handle multiple operations.
For CLI tools, it's often the case that you need to do stuff serially anyway,
so async actually becomes a problem, in terms of arranging those serial
operations.
In this case, I think parsing sync is most likely fine. Especially given
the timings provided - thx @vladimir-kotikov
Should also note that node v4 has added a callback to send() to fix this.
Doesn't help for node < v3, but you could hack a 1 sec timeout to "emulate" it
(under most conditions anyway). Smells bad, but prolly would work.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org
For additional commands, e-mail: dev-h...@cordova.apache.org
