3 ms·
I'm amazed that Chrome and Firefox load instantly and they regularly interpret scads of DOM input and complex JavaScript code. Exactly why can't emacs do this
by chris_wot 10y ago
I'm amazed that Chrome and Firefox load instantly and they regularly interpret scads of DOM input and complex JavaScript code.
Exactly why can't emacs do this again?
- db48x 10y agoThe first time you start Firefox, it reads in a whole mess of xul, html, css, and javascript. It parses it all and then dumps it to a binary file that can just be mmap'd back in next time. This is exactly like emacs, except that emacs also dumps out all of its own internal state including the state of the allocator; that makes it more fragile.