Re:Electron 3.0.0-beta.1 – Chrome 66 and Node 10
by greggman on Thursday June 21, 2018 @02:24PM
(#17367939)
Microsoft had HTML apps as a standard feature of windows in the 90s iirc
Re:Electron 3.0.0-beta.1 – Chrome 66 and Node 10
by pjmlp on Thursday June 21, 2018 @03:09PM
(#17368345)
And they are first class citizen on UWP (aka WinRT), long before Electron was a thing.
Re:Electron 3.0.0-beta.1 – Chrome 66 and Node 10
by dvlsg on Thursday June 21, 2018 @04:26PM
(#17368978)
To be fair, .NET has the capability to release applications with all the pieces required in a single exe. At least core does, anyways. That's a pretty big selling point for golang, as well, in my mind. Electron is the same thing in my mind, just on a much larger scale. Maybe it's too large to be sustainable in the long term, but there are definite benefits to having a single, self contained package.
Re:Electron 3.0.0-beta.1 – Chrome 66 and Node 10
by voltagex_ on Thursday June 21, 2018 @07:04PM
(#17369965)
They're still not there with the Golang-style single exe for .NET Core. The default behaviour of the dotnet build tool seems to be to build a .dll file (!)
Re:Electron 3.0.0-beta.1 – Chrome 66 and Node 10
by pjmlp on Friday June 22, 2018 @01:40AM
(#17371637)
Have you looked into "Self-contained deployments"?
https://docs.microsoft.com/en-us/dotnet/core/deploying/
On the Windows side, .NET Native does static linking.
We already download programs off the internet and let them run with local privileges all the time, it should be possible to safely and securely extend the capability to programs delivered as html+css+js.
Also I don't see why Electron+node isn't installed system-wide like Java or .NET. Yes, I know it's because node is a server technology whose devs aren't interested in being Java, while the people shipping electron apps are just interested in the lowest friction to deploying native apps to customers, but it still seems like the kind of thing someone would have done already if only just to show off.