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

Improving startup time in Atom with V8 snapshots

blog.atom.io

Post reply on HN
Print view View original

11–20 of 173 posts

Re: Improving startup time in Atom with V8 snapshots

#12

Post by markdog12 »

rcfox wrote: post #4

Oh man, I wish I could use snapshots in the browser. In some extreme cases, I'm dealing with multi-minute startup times.

I think v8 does cache machine code in some cases. There are a couple of flags in chrome://flags you'll want to look at:

V8 Caching Mode, V8 caching strategy for CacheStorage

https://v8project.blogspot.ca/2015/07/code-caching.html

Edit: Not the same as snapshots mentioned in the article

Re: Improving startup time in Atom with V8 snapshots

#14

Post by ruleabidinguser »

chickenfries wrote: post #3
madamelic wrote: post #2

Or you can not have a text editor in a browser. :) Cool article regardless

Must every thread about VSCode and Atom start the same way? It's a trade off: performance for a cross platform JavaScript app development. If that is a tradeoff you don't have to make, don't do it. Atom and VSCode have made that tradeoff. I don't know what rehashing this can possibly accomplish.

I don't really see what the benefit of JavaScript app development is. You don't need to use electron and JavaScript for portability, as far as I'm aware. For example, I know of Qt, and I'm sure there are other toolkits in other similarly mature platforms.

This seems destined to go the way of emacs. This is always what happens when an idealistic perspective wins out over a practical one in a development team.

Re: Improving startup time in Atom with V8 snapshots

#15

Post by Klathmon »

hartator wrote: post #7
chickenfries wrote: post #3

Earlier quoted context omitted.

Must every thread about VSCode and Atom start the same way? It's a trade off: performance for a cross platform JavaScript app development. If that is a tradeoff you don't have to make, don't do it. Atom and VSCode have made that tradeoff. I don't know what rehashing this can possibly accomplish.

It's a bit the same issue then something like rails. Easy in the short run, but when you starting doing advance optimization - likw those - you wonder why not rewrite in a more performance oriented language.

Because the whole point of the editor is the web stack.

The fact that it's built on web technologies, and web developers can make plugins easily and quickly and can hack on the core code is the entire reason for it's existence, and why it's so popular.

If you rewrite it in another stack, you basically just created an entirely new editor which isn't compatible in just about every way with atom.

Re: Improving startup time in Atom with V8 snapshots

#16

Post by chickenfries »

ruleabidinguser wrote: post #14
chickenfries wrote: post #3

Earlier quoted context omitted.

Must every thread about VSCode and Atom start the same way? It's a trade off: performance for a cross platform JavaScript app development. If that is a tradeoff you don't have to make, don't do it. Atom and VSCode have made that tradeoff. I don't know what rehashing this can possibly accomplish.

I don't really see what the benefit of JavaScript app development is. You don't need to use electron and JavaScript for portability, as far as I'm aware. For example, I know of Qt, and I'm sure there are other toolkits in other similarly mature platforms. This seems destined to go the way of emacs. This is always what happens when an idealistic perspective wins out over a practical one in a development team.

It's a benefit if your engineers already know JavaScript, obviously.

Also, emacs is one of the most successful text editors so I'm not sure I get your comparison.

Re: Improving startup time in Atom with V8 snapshots

#18

Post by [deleted] »

markdog12 wrote: post #12
rcfox wrote: post #4

Oh man, I wish I could use snapshots in the browser. In some extreme cases, I'm dealing with multi-minute startup times.

I think v8 does cache machine code in some cases. There are a couple of flags in chrome://flags you'll want to look at: V8 Caching Mode, V8 caching strategy for CacheStorage https://v8project.blogspot.ca/2015/07/code-caching.html Edit: Not the same as snapshots mentioned in the article

[deleted]
Post reply on HN