Re:Electron v5.0 Timeline
by stabbles on Tuesday February 05, 2019 @01:06AM
(#19083314)
Yes, that would be very useful to have. Some runtime, or some central application, so that the user just has to download some HTML, CSS and Javascript -- not a complete copy of Electron each time. And if this application could be used to browse the internet when the user enters a URL, that would be useful too! Game changer!
[ Parent
| on HN ]
Yes great idea! The different applications (or URLs) could be opened simultaneously and displayed as ‘tabs’ for the user to manage in the central application.
I get the joke, but an Electron "player" daemon seems like a decent idea. It could manage getting the right runtime versions, installing apps, deduping assets and granting permissions.
It'd be a sort of cross-platform Google Play Services.
That would also allow to call one application from another, just assigning some reserved namespace or domain and appending the feature at the end, kind of a path. Exciting times!
How would one remember a collection of these namespaces or the current place within one location? Analogous to physical paper, could we repurpose the concept of a "bookmark"?
Re:Electron v5.0 Timeline
by barrystaes on Tuesday February 05, 2019 @03:01AM
(#19083670)
To avoid having to update these files on your pc, these could be served by a "server" on the internet. We would have to run cables around the earth so everyone can benefit.
Unfortunately, that would also introduce latency. Plus, I'd like to be able to access these files when I'm not connected to one of these "servers".
First thing we'd have to serve then is some place where stuff like that can be discussed though, maybe some sort of "forum" with "comments" and stuff?
Re:Electron v5.0 Timeline
by murukesh_s on Tuesday February 05, 2019 @03:08AM
(#19083691)
You probably don't need electron to do that, it could be done by any end user. Wondering why it isn't being done!
Re:Electron v5.0 Timeline
by de_watcher on Tuesday February 05, 2019 @05:58AM
(#19084243)
Oh, you're too brutal to the webdev community. Don't do that. :D
Everyone likes this idea until the HTML, CSS, and JS are given the ability to change application menus and access the file system. Then oh no, we can't have that.
Instead we are encouraging users to download arbitrary binaries bundled with a browser that can be controlled and updated remotely. It’s not clear to me this is any safer.
Surely you can fix that without having physically separate copies of the underlying chromium engine?
edit: I realize now this is a joke thread... whoosh.