Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Electron v5.0 Timeline

electronjs.org

Post reply on HN
Print view View original

21–30 of 101 posts

Re: Electron v5.0 Timeline

#21

Post by arbie »

dewiz wrote: post #20
aserafini wrote: post #19

Earlier quoted context omitted.

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.

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

#22

Post by basil-rash »

no_wizard wrote: post #7
yodon wrote: post #4

Looking over the donors page, I'm pretty amazed at slack's absence. Ditto for Microsoft Teams. Way to give back to the community.

To be fair, Microsoft now pays the bills for the entire company, since electron is Githubs project as I have come to understand it

Which makes me wonder: where do the donations actually go? It looks like the total amount is less than 15k, so everything donated is very easily overshadowed by MSFT's contributions, and I don't see any hints at a payment-for-contributions program on the electron github.

Re: Electron v5.0 Timeline

#23

Post by Vinnl »

flukus wrote: post #18
pjmlp wrote: post #15

Earlier quoted context omitted.

Cough, PWA. https://docs.microsoft.com/de-de/microsoft-edge/progressive-...

Probably OK for some uses, like when you publish as a web app anyway, but for others it burdens you with keeping up with the aggressive release cycle of browsers.

Luckily web browsers take care to "never break the web" and remain backwards-compatible, so that should not be that much work.

Re: Electron v5.0 Timeline

#24

Post by twhb »

kethinov wrote: post #13

Does anyone know if the idea of creating a runtime mode for Electron is on the roadmap? (A runtime mode would be allowing multiple apps to share one installed Electron dependency rather than bundling Electron with every Electron app.)

Java-based GUI applications have been moving from the system's JVM to bundling one due to longstanding and seemingly unfixable reliability and ease of use problems. Why will Electron be different?

Re: Electron v5.0 Timeline

#25

Post by jointhefuture »

Vinnl wrote: post #23
flukus wrote: post #18

Earlier quoted context omitted.

Probably OK for some uses, like when you publish as a web app anyway, but for others it burdens you with keeping up with the aggressive release cycle of browsers.

Luckily web browsers take care to "never break the web" and remain backwards-compatible, so that should not be that much work.

I love your sarcastic response.

Favorite recent example, Chrome's audio blocking solution pretty much broke every HTML5 game in existence. 1000s of sites are still broken. To just name some easy categories, every Pico-8 game exported to HTML5, Every Unity and Unreal game exported to HTML5. Even 100s of Google's own Doodles, examples, promotions, etc ... until they pre-whitelisted every domain they own.

The worst is Apple. Trying to do anything game related in a webpage on iOS Safari is a nightmare and is pretty much guaranteed to break with each new iOS release. "minimal-ui" (nope, took that way), "user-scalable" (worked but they keep changing the conditions so old games break and have to reverse engineer under what conditions it's respected). I recently noticed one of my sites broke for audio. No errors, no mention of what changed that I can fine, worked 6 months ago, stopped working, Safari only. Note it's a site about audio and it doesn't start that audio until the user clicks the "Play" button. It's using the "resume" api but no sound comes out. Still works in Firefox and Chrome (after having to update it last year for Chrome's breaking change)

Re: Electron v5.0 Timeline

#26

Post by jasonkester »

Vinnl wrote: post #23
flukus wrote: post #18

Earlier quoted context omitted.

Probably OK for some uses, like when you publish as a web app anyway, but for others it burdens you with keeping up with the aggressive release cycle of browsers.

Luckily web browsers take care to "never break the web" and remain backwards-compatible, so that should not be that much work.

I didn't see any sarcasm tags on your comment, so I'll take it at face value and disagree. Two quick examples:

Google Chrome went from proposing a new WebAudio method called "start" to deprecating and removing the "noteGrainOn" method it renamed in the span of 12 months. Any sites using the original spec stopped working, some within a year of being released with the latest and greatest spec, one of which was Google's "WebAudio Playground" demonstration site. (There's a fun bug on file where that team had the browser team push back the method deprecation by a release so that they could fix that one website).

Google released Polymer in 2015 or so. Apps written using the latest version of that in late 2015 stopped working at some point in 2017 on Google Chrome.

Web browsers stopped being even a little bit backwards compatible around 10 years ago.

Re: Electron v5.0 Timeline

#27

Post by jointhefuture »

basil-rash wrote: post #22
no_wizard wrote: post #7

Earlier quoted context omitted.

To be fair, Microsoft now pays the bills for the entire company, since electron is Githubs project as I have come to understand it

Which makes me wonder: where do the donations actually go? It looks like the total amount is less than 15k, so everything donated is very easily overshadowed by MSFT's contributions, and I don't see any hints at a payment-for-contributions program on the electron github.

The donations go by paying the salaries of most of the top electron devs since they work for github which is owned by Microsoft.

Re: Electron v5.0 Timeline

#28

Post by paxys »

yodon wrote: post #4

Looking over the donors page, I'm pretty amazed at slack's absence. Ditto for Microsoft Teams. Way to give back to the community.

The top donor on that page is Facebook, which has given $9,000 total. Next highest is $745. Just a few commits' worth of development time costs a lot more than that, and both Microsoft and Slack have been major contributors to Electron.

Re: Electron v5.0 Timeline

#29

Post by pjmlp »

flukus wrote: post #18
pjmlp wrote: post #15

Earlier quoted context omitted.

Cough, PWA. https://docs.microsoft.com/de-de/microsoft-edge/progressive-...

Probably OK for some uses, like when you publish as a web app anyway, but for others it burdens you with keeping up with the aggressive release cycle of browsers.

Agree, but it isn't like OSes also don't change their API space or behaviors.

Unless one only cares about fossilized UNIX and Win32.

Re: Electron v5.0 Timeline

#30

Post by pjmlp »

twhb wrote: post #24
kethinov wrote: post #13

Does anyone know if the idea of creating a runtime mode for Electron is on the roadmap? (A runtime mode would be allowing multiple apps to share one installed Electron dependency rather than bundling Electron with every Electron app.)

Java-based GUI applications have been moving from the system's JVM to bundling one due to longstanding and seemingly unfixable reliability and ease of use problems. Why will Electron be different?

Java applications can compile to native code and remove needless bloat via linking.

So when is Electron going to support the same features?

Post reply on HN