Square peg, round hole. Electron just gives you a hammer to make it fit anyway :)
Thank you.
No trickery, no hidden browser windows, just normal native executables.
Java also solves the cross-platform issue, though it's GUIs tend to not look native (As opposed to Lazarus above, which is native).
If you're impressed by a webserver being able to interact with the OS for things like accessing files or databases, your mind will be absolutely BLOWN when you learn real native development.
Java does solve part of this but some people would rather use JavaScript than Java. Even if they know how to use both believe it or not.
However, if one of your platforms is the web browser, nothing is going to work better than a web view if you want a cross platform solution. Slack for example works almost exactly the same in my web browser as it does in electron. If you want a solution that works on Linux, MacOS, and Windows AS WELL as the web browser then the web view approach is pretty obvious.
Lastly the JavaScript web development experience is great with hot module relacement and Chrome’s developer tools. Not to mention the JavaScript open source community is amazingly strong and there is a lot of innovation going on. To simply dismiss all of this because of personal reasons is fine by me but I don’t agree with your view.
Making absolute statements about why people make certain choices or believing them can definitely lead to false conclusions. People don't only use cross platform toolkits because they do not want to do work. Sometimes it is the best solution given the features and constraints. I like to think of it as being pragmatic.
I don't think anyone is "impressed" by it. It is just useful. The point of electron is being able to write javascript applications that run on multiple platforms.
Using Lazarus (and Pascal) means you need to learn another language to write native applications from the one you use to write web applications.
I'm not taking a position here, I am just pointing out the pros and cons. I am neither a javascript nor pascal programmer so I have no dog in this fight.
Java apps on the desktop became more prevalent and usable when Java was bundled in. The Electron is not so different from what worked for Java.
Plus it gets rid of visual clutter like the tab bar and treats your app like an actual application rather than a simple website for viewing.
People using desktop toolsets never even have to think about that "problem" because it just doesn't exist when you're using the right tools.
There are three types of tools for every job..
* The right kind
* The wrong kind
* The wrong kind but we'll make it work
Electron hits squarely in the third category by hiding the browser and webserver and pretending it's a real desktop application.
As soon as you move to the desktop, you're competing with the desktop toolsets.
People comparing Electron to the browser is missing the entire point of what Electron is for, which is pretending to be a native application.
If you want to write software for a platform, write software for that platform. Don’t write software for some other platform, try to make it fit, and then declare it good.