Google Enhances Chrome Speed With Background Javascript Compilation

4

Comments

+ Add a Comment
avatar

vrmlbasic

Google named their javascript engine after a gas-guzzling internal combustion engine? How very not green of them.

I guess this is a good idea but it is pretty tragic that it has taken this long for us to get to it.

avatar

AFDozerman

I sure hope you're kidding...

--

I personally don't think so. There are a lot of other features that should have the attention of the developers in this day and age when the real bottleneck is the connection and not the rendering engine. This is one reason that I stuck with the old Opera for so long before they scrapped their old browser and pretty much created an Opera-themed chrome. In the end, I'm glad Google handled pre-loading links and stability before improving speed any more.

avatar

vrmlbasic

I was joking. I couldn't pass up the opportunity to point out that the company that got goats to mow its grass (in order to be "green") referenced the "anti-green" V8.

I'm not touching Chrome with a ten-foot pole but I do like to hear about programs taking further advantage of threading and multiple cores.

avatar

AFDozerman

Sorry if I came across a little too serious; you can never be too careful on 'The Internet'... but seriously? GOATS? Who's genius idea was that?? They *do* realize that most grazing animals need more than just grass to stay healthy, right? I would've gotten my ass whooped if I had forgotten to take the cow's salt blocks and grain out when I was growing up on the farm. I guess they're hiring people to come out and give these goats the same treatment? Or maybe they're just letting them starve and scratching their heads over all the dead goats lying around GoogleHQ...

--

I can agree there. It seems some developers missed the notice about Moore's Law slowing down and the world needing to go parallel to keep up.