David Sharp

I think it's the sensible default going forward, also worth noting is the caveat that `setFromResponse` and `getFromResponse` are missing this functionality altogether (#72)

console.frog on a console.log, I like it

Seeing this problem in v0.4.2 on macOS too

I don't see what problem this solves that Cordova doesn't. And by trying to match the existing API, I can only imagine how much of it will work slightly differently/not...

I think `fs` more than anything highlights the fact that this can't simply be a drop-in without making assumptions about other people's apps. Both iOS and Android have specific expectations...

@kinnalru, that definitely sounds interesting, but does it solve any problems the `electron-mobile` project might have? Sounds as if it would create _more_ barriers for both developers and users.

@gabrielcsapo, I think the issue with the Electron API is that while we're talking about hybrid apps in both desktop and mobile cases, a lot of desktop concepts don't match...

@Ad5001 Sure, the main BrowserWindow would need some kind of polyfill-type solution, but they're such different beasts that you can't just pretend they're the same because you'll find more differences...

We should be leveraging Electron's tech and design _principles_, not crowbarring everything it offers into a different environment. I think specifically supporting some and not all of Electron's APIs is...

The way I see it, it should be a Node module in a similar vein to Electron, Cordova, React Native, etc. I also agree with using `standard`, but specifically for...