3 ms·
V8 is the js engine. The one that is so fast because it compiles in JIT, the one that powers Chrome and Node.js, the one that enabled a full range of let's-buil
by tajen 11y ago
V8 is the js engine. The one that is so fast because it compiles in JIT, the one that powers Chrome and Node.js, the one that enabled a full range of let's-build-a-full-app-in-a-browser apps.
Also for the worse: the one that lets us include 10Mb of js in a browser.
- coldtea 11y ago>The one that is so fast because it compiles in JIT That's true for all modern JS engines (JavaScriptCore, Edge, SpiderMonkey, v8) and has been for several years (almost a decade).
- Cthulhu_ 11y agoBut only after V8; before that, JS performance had no priority in browsers.
- azakai 11y agoThat's a common mistake, but JITs in WebKit and Gecko came out at around the same time as v8. Their development began before v8 launched. edit: For example, see the dates on Wikipedia, v8 launched September 2008, and WebKit's Nitro (SFX) JIT launched in the same month. https://en.wikipedia.org/wiki/WebKit#JavaScriptCore https://en.wikipedia.org/wiki/WebKit#JavaScriptCore https://en.wikipedia.org/wiki/V8_(JavaScript_engine) https://en.wikipedia.org/wiki/V8_(JavaScript_engine)
- coldtea 11y agoNope. In fact Mozilla was somewhat earlier to come up with their JIT-ed JS engine, then Google (v8), then Apple (JSC), but all went live with an insignificant time difference between them (all within a few months in 2008). (Insignificant since the respective companies have already been working on them simultaneously for years -- so going live was mostly based on who wrapped up first, bugs be damned, not on some unique innovation that others later copied).