Google Chrome: It’s not about the browser

Javascript and java are not even close, javascript is a scripting language that gets excecuted in your browser. So if a site or page uses lots of javascript the source needs to be downloaded to the client browser and makes the bandwidth usage much more.

How fast the javascript is excecuted depends entirely on the browser.
 
I agree that the standards aspect of the web is catching up, at least in the standards development direction. However lost of developers don't really give a damn about standards compliance and with no body to force adoption of and compliance to the standard this will be the case for a long time.
 
I agree that the standards aspect of the web is catching up, at least in the standards development direction. However lost of developers don't really give a damn about standards compliance and with no body to force adoption of and compliance to the standard this will be the case for a long time.

This might be true, eventually though quirks mode in browsers will become extremely unreliable. Can you think of any other programming language that allows incorrect code to be displayed correctly...?
 
Javascript and java are not even close, javascript is a scripting language that gets excecuted in your browser. So if a site or page uses lots of javascript the source needs to be downloaded to the client browser and makes the bandwidth usage much more.

How fast the javascript is excecuted depends entirely on the browser and the internet connection.
Fixed.
 
This might be true, eventually though quirks mode in browsers will become extremely unreliable. Can you think of any other programming language that allows incorrect code to be displayed correctly...?

Blame the browsers makers (and especially the browser wars of the mid nineties) for that one.
 
Javascript and java are not even close, javascript is a scripting language that gets excecuted in your browser. So if a site or page uses lots of javascript the source needs to be downloaded to the client browser and makes the bandwidth usage much more.

How fast the javascript is excecuted depends entirely on the browser.

If common used functions is bundled as an external .js file, it's downloaded only once, and stored in the cache from there on, which makes frameworks and libraries great!

Don't know if you've noticed but you can even include frameworks directly from google code these days, so that means that if a user has visited any site that also uses it, it doesn't need to be downloaded again.
 
I wonder when the Linux version is going to be released....and the Apple version.....and the....(you name it)....version?
 
Sounds like hype. But I'm waiting for Chrome to come out of beta. At the moment it's got too many problems to be a serious contender against Firefox.
 
Don't know if you've noticed but you can even include frameworks directly from google code these days, so that means that if a user has visited any site that also uses it, it doesn't need to be downloaded again.

Not I haven't but it sounds cool. I can imagine it can be a great help. Of course then you don't have control over the frameworks you use.
 
I'll just wait for FireFox to release the so called "V8 engine", since Google and FireFox have regular lunch breaks together. :D

I think that is what Google wants in the end and what this article tried to explain.
 
Sounds like hype. But I'm waiting for Chrome to come out of beta. At the moment it's got too many problems to be a serious contender against Firefox.

That's the problem with Google. A lot of their products stay in BETA...
 
Top
Sign up to the MyBroadband newsletter
X