11 ms·
Electron 3.0.0
- draw_down 8y agoIt's the runtime you all love to hate!
- M4v3R 8y agoI 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 8y agoOh look, finally you are getting some API that has existed on proper frameworks for more than a decade.
- hnbroseph 8y agoyes, it's pretty nice to get new stuff :D
- LeoNatan25 8y agoWould you also like a lollipop? You can get one at the kids JS "dev" table.
- dang 8y agoPosting uncivilly will get you banned here, so please don't do this again. https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- giancarlostoro 8y agoIt 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 https://electronjs.org/releases#3.0.0-beta.1
- jonny_eh 8y agoThanks, 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.
- MBCook 8y agoAs someone who doesn’t follow Electron even that is worthless to me. Is there a significant speed/memory usage change? Is the install smaller? Some new features that people want? I don’t know. And I’m not going to read the names of dozens of tickets to try to find out.
- LeoNatan25 8y ago> Is there a significant speed/memory usage change? Is the install smaller? Some new features that people want? No, it still packages two different runtime environments, one of which is a browser, which, in turn, is basically an OS.
- MBCook 8y agoI know it’s not going to be native speed. Every. But I thought maybe it was 10% faster or something due to an updated JS engine. (Just a guess at a possible feature, not meant to be true)
- Ajedi32 8y agoWell, they updated to a new version of V8. So that's about 8 months worth of JS optimizations and new language features right there. The change log doesn't really do a good job of highlighting that though, it just says "Upgraded from v8 6.1.534.41 to 6.6.346.32."
- MBCook 8y agoI figured it would include the latest version, but 6.1 to 6.6 is meaningless numbers to me. In a list of this style it makes sense, I just wish this was an announcement that said ‘we changed/added X, Y, and Z. V8 has been updated to a version with a faster GC. MacOS looks more native. And (other cool change)”. Just a little paragraph like that would be great.
- seanalltogether 8y agoI 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
- mkonecny 8y agoWhy is it taking 100% CPU to play gifs?
- seanalltogether 8y agomaybe not 100% from doing a quick test, more like 30% nowadays but that can use up power quick still
- LeoNatan25 8y agoChromium is notoriously slow at rendering GIFs. It used to be faster than Firefox, but years ago it went downhill. On a forum I visit, people would basically troll Chrome users by posting hundreds of animated smilies. On Firefox and Safari, there is little effect, while it chugs Chrome down to a halt.
- Razengan 8y agoIs 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.
- LeoNatan25 8y agoShsh, or you’ll burst the web “devs” bubble of “write once, run nowhere, rewrite multiple times, run like shit here and maybe there”.
- burtonator 8y agoI'm working on shipping a new release of my document annotation platform on Electron 3.0 https://github.com/burtonator/polar-bookshelf 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.
- cordite 8y agoWill electron apps finally stop canceling OS X shutdown / restart (before quitting themselves)? Atom, Slack, and others each prevent shutdown one at a time.
- johnthedebs 8y agoThey should, yes. That bug was actually fixed in one of the 2.0.0 betas (https://electronjs.org/releases#2.0.0-beta.1 https://electronjs.org/releases#2.0.0-beta.1) – those apps may just be slow to catch up.
- cordite 8y agoFrom February? That is quite old as far as web apps go
- Forge36 8y agoI'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 https://github.com/electron/electron/pull/13760
- nevi-me 8y agoOut 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 8y agoCurrently 'npm i -D electron@latest' is still installing electron@2.0.10 but 3.0 can be installed with 'npm i -D electron@3.0'.