V8: an open source JavaScript engine


 
   

Google engineer, Lars Bak, explains the key engineering decisions behind, V8, the JavaScript virtual machine used in Google Chrome.

Canal: Science & Technology
Añadido: December 31, 1969 at 5:59 pm
Autor: Google

Duración: 05:21
Puntuación: 4.81
Reproducciones: 24956

Etiquetas: browser.  chrome  developer  google  Javascript  open  source  v8  

Recomienda este vídeo

Agregar a Favoritos!



Video URL:


Insertar:

Comentarios de http://www.cantaecuador.com

Comentarios de YouTube

C7B27D7B4 (December 31, 1969 at 5:59 pm)
we need more, better browsers; we don't need one big browser that everyone uses---we had that with ie and it didn't work; diversity and cooperation are what we need;any sensible attempts to speed up js are welcome :-)
akbg (December 31, 1969 at 5:59 pm)
Well, please, instead of repeat "RTFM" can you tell me where (do you think) I'm wrong?
thenduk (December 31, 1969 at 5:59 pm)
You're a joke. Seriously, wikipedia.
akbg (December 31, 1969 at 5:59 pm)
Well, if you run a 32-bit application on top of a 64-bit processor you can't utilise all the added registers included in x86-64 instruction set, so you're theoretically right but practically slightly wrong.(In fact a 64-bit application can be even slower of a 32-bit one if they make massive use of pointers, because they allocate more RAM and so they provoke more cache and memory faults.)
thenduk (December 31, 1969 at 5:59 pm)
Eh, no dude. It's not 'only 10 percent faster'... see, 64 bit means that integers are 64 bits long rather than 32... It has exactly nothing to do with 'speed' of any sort. There is no 'emulation' going on, either.I'm not going to continue this discussion, however, since what you need is not a thorough owning from me but instead a trip to wikipedia.
Me04120 (December 31, 1969 at 5:59 pm)
Fuck you, if everything was 64 bit it would be faster. I have used 64 bit firefox and it blows 32 bit out of the water. Don't bring the bullshit argument that 64 bit only allows more RAM and in reality is it only like 10 percent faster. Running 32 bit apps on a 64 bit version of windows is slow because the emulation is slow. If I had a 32 bit OS on the same computer yeah it wouldn't make much difference, but guess what I don't.
thenduk (December 31, 1969 at 5:59 pm)
You obviously dont know what '64bit' means.
Me04120 (December 31, 1969 at 5:59 pm)
The thing that pisses me off is that there still isn't a flash plugin or java plugin that can work in any 64 bit browser. If I could use a 64 bit browser for everything, things would be so fast.
steblublu (December 31, 1969 at 5:59 pm)
they made Chrome & V8 to encourage development of their Android platform.
Me04120 (December 31, 1969 at 5:59 pm)
Basically, they made V8 really fast, but TraceMonkey has been in development for like 2 months now and it's almost as fast. I'm sure that Firefox programmers are going to look at V8 and see what can be done to make TraceMonkey even better. If google wants to work on a browser I don't know why that made there own rather than contribute to Firefox. Chrome still has many problems with rendering and stuff. Plus, Firefox has such a large plugin base.