fully agree... and those (Lazarus/wxWidgets/Qt) generate native code and don't require you to ship a browser with your application...
The key feature of Neutralino (as opposed to Electron) is that it does _not_ require you to ship a browser - it provides similar developer UX to Electron, but it uses your system's existing browser so binaries are dramatically smaller (2MB for hello world) and memory overhead is minimal (~3MB for hello world).
According to (1) that is incorrect. It uses WebKitGTK+.
(1) https://github.com/Elanis/web-to-desktop-framework-compariso...
Neutralinojs says: "Neutralinojs doesn't bundle Chromium and uses the existing web browser library in the operating system (Eg: gtk-webkit2 on Linux)"
Skimming through the source code, it appears to use WebView2 on Windows - which is Edge.
Also, wxWidgets looks very strange on macOS right now. I just built some demos last week from the examples in the repo for wxLua and they looked awful. I have no idea what was going on because as far as I remember wxWidgets would just be calling the native stuff. Still, they looked unusable.
This shouldn't be the case. If you use wx 3.0, it's too old to support the features that appeared in macOS after its release (dark mode etc), but 3.1.5 should look just as the native UIs do.
Edit: this was NOT meant to imply the browser component is loaded. This was a reply to the first comment with regards to what frameworks can and can not do.