Re:How Four Native Developers Wrote an Electron App
by GRiMe2D on Friday May 19, 2017 @01:12AM
(#14373179)
While nodejs is fast enough, Electron and apps built on it aren't fast. Electron is a mix of Chromium and nodejs. Chromium's rendering isn't meant to be used as desktop app. Especially for laptops. I have a MacBook pro mid 2010 with two GPUs. Integrated GPU uses less battery energy than discrete one. And every Chromium app switches GPU to discrete one and causes battery drain.
[ Parent
| on HN ]
Re:How Four Native Developers Wrote an Electron App
by dragonwriter on Friday May 19, 2017 @01:30AM
(#14373249)
> Chromium's rendering isn't meant to be used as desktop app.
Yes, it is. That was pretty much the entire point of Google making Chrome (to make web apps have acceptable parity with desktop apps), and the entire premise of them building on Chrome with ChromeOS.
Now, it may not satisfy you in that role, but it absolutely is meant for it.
Re:How Four Native Developers Wrote an Electron App
by murukesh_s on Friday May 19, 2017 @01:30PM
(#14377749)
Good point. People are bashing Electron and chromium in general. But they do forget JVM based IDEs had the same problem. Rather than bashing Electron, if we can figure out to make it more leaner and faster, it would be much better.
Re:How Four Native Developers Wrote an Electron App
by LeoNatan25 on Friday May 19, 2017 @06:03PM
(#14379673)
"We"? You mean people that know C++ and low level native APIs, right? Which is decidedly not you. You are building a "hackable" "node.js" "npm" "app". The problem is, people who are indeed capable of making some improvements, including people on the V8 and WebKit teams themselves, do not believe in what these tools attempt to accomplish. (Listen to Don Melton's interviews on the subject, for example.)
I say "some improvements, as the problem cannot be solved completely; you'd understand why if you understood the underlying technology.