Electron is a widely hated framework on Linux, but what about the alternatives like Neutralinojs?
In their own words: In Electron and NWjs, you have to install Node.js and hundreds of dependency libraries. Embedded Chromium and Node.js make simple apps bloaty — in most scenarios, framework weights more than your app source. Neutralinojs offers a lightweight and portable SDK which is an alternative for Electron and NW.js. Neutralinojs doesn’t bundle Chromium and uses the existing web browser library in the operating system (Eg: gtk-webkit2 on Linux). Neutralinojs implements a secure WebSocket connection for native operations and embeds a static web server to serve the web content. Also, it offers a built-in JavaScript client library for developers.
Do you experience alternatives like Njs to blend more in the desktop layout, install less junk, use less memory, are more compatible with Wayland,…?
The thing is, Linux Desktops dont have a unified WebView. I wonder how that would work on KDE and others
Tauri uses webkitgtk everywhere, including KDE.
Hm, I mean that is way better than using an entire Chrome browser, but KDE uses qtwebengine
True. If their goal is truly to use the “native” solution everywhere, they should use QtWebEngine on Qt desktops. For the most part, the advantage with Tauri isn’t so much that it’s using the “native” web engine, it’s that not every Tauri application has to bundle a full (probably outdated) web engine. On Linux, this is achieved regardless of whether WebKitGTK or QtWebEngine is used. The first Tauri application you install pulls in WebKitGTK if you didn’t already have it installed, then every subsequent application just uses the same one. I’m personally glad it’s using WebKitGTK despite being a Plasma user. The less we rely on Blink and Blink-based web engines, the better. Having to spend 100MB of my 1TB hard drive on WebKitGTK to achieve this isn’t making me lose a whole lot of sleep.
I suppose that is okay, and targeting a specific engine is likely needed, to have non-trivial features.
I believe it uses gtk-webview. So on KDE system you would use GTK as a base. But you anyway would have GTK libs in your system.