So this is basically the emacs startup hack? Ugh.
I was just going to remark, those that don't know history are doomed to repeat it.
To me it seems like a fantastic way to improve startup time regardless of language or ecosystem.
11–18 of 18 posts
So this is basically the emacs startup hack? Ugh.
I was just going to remark, those that don't know history are doomed to repeat it.
To me it seems like a fantastic way to improve startup time regardless of language or ecosystem.
Earlier quoted context omitted.
Get to work on a Webassembly compiler and your wish might be granted. http://webassembly.org
The Tanks demo makes my CPU hurt (15" rMBP, Firefox). Why is WebGL still so heavy on the CPU?
So this is basically the emacs startup hack? Ugh.
So this is basically the emacs startup hack? Ugh.
for those of us who aren't familiar - what's the emacs startup hack, and why is is detrimental?
One of the big downsides (and the reason it became well known) is it's lack of portability, as it requires in-depth knowledge of the system's memory structures.
LWN article and previous HN discussion: https://news.ycombinator.com/item?id=11001796 Somewhat lower-level article that shines some light: http://emacshorrors.com/posts/unexecute.html
There are only so many brain cells on earth, can we stop using them to make javascript things on the desktop slightly less slow? Let's just not use it.
But yeah lets stop people trying to make JavaScript faster
Earlier quoted context omitted.
The Tanks demo makes my CPU hurt (15" rMBP, Firefox). Why is WebGL still so heavy on the CPU?
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?