I gave you a clear set of reasons I dislike and will not use Cordova, but I feel like you're just using it as a shield. I mean seriously, Cordova is the reason

I gave you a clear set of reasons I dislike and will not use Cordova, but I feel like you're just using it as a shield. I mean seriously, Cordova is the reason you're not a "drone in an office?" Give me a break. How about all the people who are using Cordova in their Agile drone office? It's great that you've been able to get into your own thing, but plenty of, for instance, native mobile devs have done the same. Or non mobile devs. Or full stack. Heck, I too have written, by myself, native Android and iOS apps, and their backends. I don't think that's saying a whole lot. Where did I say I was touching generated code, the cordova.js thing? Because I was trying to find the cause of our slow load in the app and stumbled through their init process into that issue. The native plugins are usually good, as you mentioned, but don't cover more complex use cases. No, I'm not going to go through and talk about all of them -- this is two or three years ago now. We wrote native plugins for the features we needed that weren't available for our use cases, and it seems likely that any advanced app will end up needing to. Your point about "compounding pain" is exactly how I feel about Cordova, because as I mentioned, it's as complex if not more in a hybrid app. You're fighting the build system, the js engine, the layout engine, etc. It's not as though you get it all for free because it's javascript. It's great to enjoy your tools, and again, I'm glad you're able to make an independent living off it, but to claim that it's some sort of life changing tool the whole mobile world needs to take more seriously isn't realistic. And again, as far as new development, I'd love to hear people who are considering going the hybrid route chime in, but I at least don't know of anyone or any companies who are or would go that route.