Github user jimmont commented on the pull request:
https://github.com/apache/cordova-js/pull/118#issuecomment-181090801
@nikhilkh Yes. Throwing errors is a reliable way of both debugging and
finding problems. When they're intercepted I can't do that as easily. (Similar
is true of `cordova-plugin-console`.) In looking through the source cordova
uses a module loader and http requests to setup **global** APIs from the
**local filesystems** on the device, and various events/event-system to get the
sequence and setup right. Seems sub-optimal to me. (For example, a concatenated
script which works with the global namespace directly seems like the simple
approach, all things considered, and is what happens in the end anyway.) But I
haven't finished looking at all the contemporary platforms (that I want to
target anyhow). No one asked for these observations but given I'm seeing them,
and how expensive time-wise it is to work either with or around them, thought
I'd mention it. (In case more context is helpful: imagine debugging getting
cordova and all the desired plugins working in a worker so the UI is mor
e responsive. By all appearances the original authors didn't plan for this
scenario.)
---
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
