Re:Energizing Atom with V8's custom startup snapshot
by slackingoff2017 on Thursday May 04, 2017 @02:26AM
(#14262905)
Can we just compile js to bytecode? It's silly making huge apps in a language that has to be parsed and compiled on the fly
[ Parent
| on HN ]
Re:Energizing Atom with V8's custom startup snapshot
by pritambaral on Thursday May 04, 2017 @05:32AM
(#14263641)
That would reduce largely the JavaScript runtime size, but not the rendering engine and all the vendored third-party libraries.
On my Arch Linux installation, the node.js package takes about 18.45 MiB on disk. While I'd be glad if the various multiple electron runtimes slimmed down by 10-15 MiB, it wouldn't be much.
Re:Energizing Atom with V8's custom startup snapshot
by astrodust on Thursday May 04, 2017 @03:02AM
(#14263068)
Get to work on a Webassembly compiler and your wish might be granted.
Re:Energizing Atom with V8's custom startup snapshot
by spiderfarmer on Thursday May 04, 2017 @04:14AM
(#14263352)
The Tanks demo makes my CPU hurt (15" rMBP, Firefox).
Why is WebGL still so heavy on the CPU?
Re:Energizing Atom with V8's custom startup snapshot
by josh64 on Thursday May 04, 2017 @05:44AM
(#14263684)
It works fine on my 2011 15" macbook pro with Firefox 54.0b4. I wonder if it is the high retina resolution thats the problem for you?
Re:Energizing Atom with V8's custom startup snapshot
by spiderfarmer on Sunday May 07, 2017 @03:16PM
(#14287031)
It might be because the macbook is also driving a 4k display at the same time.
Re:Energizing Atom with V8's custom startup snapshot
by CyberDildonics on Thursday May 04, 2017 @08:07AM
(#14264192)
It takes up about 2 percent of my 7 year old cpu in chrome. It is also compiled from Unity, so was not made from C++ directly.
Re:Energizing Atom with V8's custom startup snapshot
by slackingoff2017 on Thursday May 04, 2017 @04:27AM
(#14263412)
Apple's OpenGl support is crap.