Stupid question: instead of embedding an entire browser in each-and-every app and trying to keep that secure, why not package the native desktop framework as a shared, versioned component and the app as a tiny thing that depends on it?
NeutralinoJS: Lightweight Electron alternative using native browser controls
21–30 of 200 posts
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#22> There are some drawbacks such as Windows edition is based on IE etc. What does this mean?
It uses whatever the system webview is. So on Windows that is IE, on Mac it’s WKWebView, not sure about Linux. It’s a trade off: it’s much more lightweight but loses cross platform consistency. For some that might be absolutely fine, for others it may not.
I wish we had a step inbetween. Something more than "just a webview" but something less than, well, all of electron. Give me like a really cut down browser that's consistent across platforms and embed it.
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#23Stupid question: instead of embedding an entire browser in each-and-every app and trying to keep that secure, why not package the native desktop framework as a shared, versioned component and the app as a tiny thing that depends on it?
Not a stupid question. This is exactly how operating systems and application SDKs were always developed and deployed until fairly recently.
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#24Stupid question: instead of embedding an entire browser in each-and-every app and trying to keep that secure, why not package the native desktop framework as a shared, versioned component and the app as a tiny thing that depends on it?
Google's Carlo sort of does that. It uses your system's already-installed Chrome instead of packaging another one.
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#25Stupid question: instead of embedding an entire browser in each-and-every app and trying to keep that secure, why not package the native desktop framework as a shared, versioned component and the app as a tiny thing that depends on it?
Single binary is becoming more common even for runtime apps (JVM,.NET).
The reason I wouldn't want Electron to be shared across apps is I don't want a system wide install and certainly don't want to deal runtime version type issues. Electron would start having to be backward compatible for years.
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#26The docs page is just white for me
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#27Does this support WASM? I'd expect not given it's so small, but worth asking.
That probably just depends on whether the system browser that it launches supports wasm, I think it’s passing off the dependency.
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#28Looks kind of like WebView [1] which I earnestly tried but eventually abandoned. Using the system-provided web engine is great for space savings, but terrible for cross-compatibility and feature availability owing to having to use IE on Windows. [1] https://github.com/zserge/webview
The good thing about webview is that it does not use localhost:8080 for internal comms!
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#29Looks kind of like WebView [1] which I earnestly tried but eventually abandoned. Using the system-provided web engine is great for space savings, but terrible for cross-compatibility and feature availability owing to having to use IE on Windows. [1] https://github.com/zserge/webview
[deleted]
Re: NeutralinoJS: Lightweight Electron alternative using native browser controls
#30Looks kind of like WebView [1] which I earnestly tried but eventually abandoned. Using the system-provided web engine is great for space savings, but terrible for cross-compatibility and feature availability owing to having to use IE on Windows. [1] https://github.com/zserge/webview
Isn't the "system provided web engine" now Edge on Windows 10, and has been fore a while?