3 ms·
> the really intensive javascript apps just use way too much memory in Firefox, especially when you have 12 hour Firefox sessions I suspect that huge improveme
by gwenhwyfaer 19y ago
> the really intensive javascript apps just use way too much memory in Firefox, especially when you have 12 hour Firefox sessions
I suspect that huge improvements in the state of Javascript interpreters will really start to change the equations. If JS is Lisp in disguise, there's no reason why JS engines can't start to benefit from the decades of evolution put into Common Lisp runtimes.
Come to think of it, what if a JS engine got fast enough that the browser itself could be written in Javascript?
- rms 19y agoFor now, we're getting some nice incremental improvements. Firefox 3 Alpha is worth using just for the improved JS engine.
- AF 19y agoHey gwen...what do you mean by this: "If JS is Lisp in disguise"?
- mcxx 19y agoWell, look at parenscript for example. It's quite easy to translate Lisp into JS. Moreover, the first prototype of JS engine in Firefox was written in Lisp.