Electron 3.0.0

[seanalltogether]

I really hope whatever the NativeWindow changes are allow Slack to finally stop rendering when the app goes to the background. My battery has been killed a couple times by the Slack renderer using ~30% cpu playing gifs while the app isn't visible, and their support says its because they don't have a notification hook for minimizing

[Razengan]

Is writing native apps honestly still so hard these days?

I can appreciate the concerns about maintaining multiple codebases and dealing with different delivery mechanisms and their rules, but modern iOS/macOS and Windows APIs (at least; I cannot speak for Android and Linux) seem just as easy, let you work in arguably better languages, evolve at a faster rate, and provide a better experience for users and their machines.

[stefan_]

I want to work at a company like that, where I can just blame the "stack" we're using and shrug my shoulders.

[43920]

> their support says its because they don't have a notification hook for minimizing

That doesn't even seem correct - the BrowserWindow emits "hide" and "show" events [1] that Slack could use to do exactly what you're describing. I'm guessing they just don't want to implement it for some reason?

[1] https://electronjs.org/docs/api/browser-window#event-show

[giancarlostoro]

Assuming they update soon enough I suppose. I find using the browser window for Slack is easier, the main browsers I use let you pin tabs so it's even easier, plus I can put a darker theme on Slack, so sick of the bright white background.

[dawnerd]

You can kinda disable gifs by going to preferences > Messages & Media and unchecking "Show images and files from linked websites". Doesn't get them all but it really helps.

[baxter001]

Looks like the BrowserWindow events at the js api level are unchanged for the past two years.

Here's hoping something deeper was broken about them that now drastically changes top-level api behaviour!

[mkonecny]

Why is it taking 100% CPU to play gifs?

[pacifika]

FWIW I disabled animations in the slack settings and the difference is night and day.

[giancarlostoro]

It looks like a short list of new things, so maybe it makes sense to look at the first beta for v3:

https://electronjs.org/releases#3.0.0-beta.1

[jonny_eh]

Thanks, this is the "real" changelog. I wish projects didn't waste these great PR opportunities. There should be a blog post written by a human for human consumption that explains why we should be excited.

[burtonator]

I'm working on shipping a new release of my document annotation platform on Electron 3.0

https://github.com/burtonator/polar-bookshelf

We've been releasing with the 3.0 betas for about a month now and haven't had any issues. It's been pretty stable.

Actually more stable than the 2.x series as it has a number of bug fixes that weren't in the 2.0.0 ... really glad this platform is still moving forward aggressively.

There are also 4.0 beta builds up which I haven't played with yet.

[M4v3R]

I have eagerly waited for this release, as it uses Chrome 66. Previous stable version used Chrome 61, which lacked some nice additions to JS, most notably for me - the complete Intl API support.

[LeoNatan25]

Oh look, finally you are getting some API that has existed on proper frameworks for more than a decade.

[cordite]

Will electron apps finally stop canceling OS X shutdown / restart (before quitting themselves)? Atom, Slack, and others each prevent shutdown one at a time.

[johnthedebs]

They should, yes. That bug was actually fixed in one of the 2.0.0 betas (https://electronjs.org/releases#2.0.0-beta.1) – those apps may just be slow to catch up.

[Forge36]

I'm excited, I need to dig though to see if any of the chrome updates fixed accessibility issues. The press release doesn't link the the PDF support issue which is a little worrying.

I think the fix is: https://github.com/electron/electron/pull/13760

[nevi-me]

Out of curiosity, assuming that Node 10.8 (or the latest version we're on) doesn't break anything from 10.2, and also assuming that the Node abstraction layer protects developers from underlying V8 ABI changes; why would Electron release a new version with dated versions of Node and V8?

Is it because of a release cycle?

[derfnugget]

Currently 'npm i -D electron@latest' is still installing [email protected] but 3.0 can be installed with 'npm i -D [email protected]'.