There's already such a thing for rust called alcro and for go called lorca which utilizes a pre-installed Chromium, Google Chrome or will install Chromium.
In any case, I'm still in two minds about the whole business of native apps vs. packaged web apps. If you can do such a web app right, you don't need a webview/neutralino.js/electron/nw.js installation.
Additional abilities could be added with a hybrid approach (be aware of security implications) which is then independent of the browser. The obvious advantage is that you can develop one front end for all systems and experience over different devices will be consistent. At the same time, you'll lose consistence with the UX of the OS.
Although in most cases Chrome/Chromium is already present, it might make sense to download the executable if it can not be found (for better user experience). Somehow github.com/puppeteer/puppeteer is able to do that (downloading portable chromium - github.com/puppeteer/puppeteer/blo...). This would also fix #12
If there are any volunteers to implement this - I'd be happy to merge the PR ;)
But they are installed on virtually every operating system intended for end users: browsers. The power of the web is interoperability. Why don't we wield it anymore? What happened in the last decade that everyone now insists of only supporting one single version of one single rendering engine?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's already such a thing for rust called alcro and for go called lorca which utilizes a pre-installed Chromium, Google Chrome or will install Chromium.
In any case, I'm still in two minds about the whole business of native apps vs. packaged web apps. If you can do such a web app right, you don't need a webview/neutralino.js/electron/nw.js installation.
Additional abilities could be added with a hybrid approach (be aware of security implications) which is then independent of the browser. The obvious advantage is that you can develop one front end for all systems and experience over different devices will be consistent. At the same time, you'll lose consistence with the UX of the OS.
It seems that Lorca cannot download Chrome (yet).
Although in most cases Chrome/Chromium is already present, it might make sense to download the executable if it can not be found (for better user experience). Somehow github.com/puppeteer/puppeteer is able to do that (downloading portable chromium - github.com/puppeteer/puppeteer/blo...). This would also fix #12
If there are any volunteers to implement this - I'd be happy to merge the PR ;)
I don't really understand why can't web engines be installed like Java Runtime Environment (JRE)? That is, global by default.
Maybe, breaking production is hell, but again, why not
That is, pinned dependencies, but ok with minor version updates.
But they are installed on virtually every operating system intended for end users: browsers. The power of the web is interoperability. Why don't we wield it anymore? What happened in the last decade that everyone now insists of only supporting one single version of one single rendering engine?