3 ms·
I don't have an Electron project going, but I can tell you something like this could add some value to some companies invested in Electron as-is. You just have
by giancarlostoro 10y ago
I don't have an Electron project going, but I can tell you something like this could add some value to some companies invested in Electron as-is. You just have to get their attention. I would suggest maybe resubmitting this post later if it doesn't catch the flare of intrigue. If I do end up building an Electron Project I will definitely look into Electrino when the time comes. You mention it doesn't feature all the features of Electron but is the typical browser DOM still available?
- pavlov 10y agoThanks! The full browser DOM is certainly there. The missing APIs are the Electron-specific ones that apps can use to access desktop features. Adding new APIs individually is pretty easy, but there's a lot of stuff in Electron, so reaching full coverage is of course a lot of work... That's why I'd like to try adding APIs based on usage in real-world apps, "filling in the gaps" so to speak. I wrote a blog post with some more details about the rationale behind Electrino: https://medium.com/@pauli/put-your-electron-app-on-a-diet-with-electrino-c7ffdf1d6297 https://medium.com/@pauli/put-your-electron-app-on-a-diet-wi...
- 52-6F-62 10y agoThis could be big. One of the most common complaints about Electron I've heard is the file size and cpu load. In short, nice work! I know it would add extra time to the build on the programmer end, but what about component API's -- to keep build size at a minimum while allowing access? I haven't looked at any of the code -- would this be possible? Any thoughts?