The More Popular the Browser, the Slower It Is
demishade writes "Peacekeeper, the browser benchmark from the makers of 3DMark, comes out of beta and shows an interesting (though perhaps not surprising) tidbit — the more popular a browser, the worse its performance. While it should not be surprising to anyone that IE slugs at the last place, the gap between Firefox and Chrome, is. Once IE's market share goes the way of the Dodo will web developers start cursing Firefox? How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function?"
Here we are on the Slashdot plains in Africa, looking for that most elusive of species, the First Post...
Chrome was designed with JavaScript performance as a top goal. So why are we surprised it performs well?
"No matter where you go, there you are." -- Buckaroo Banzai
So does this mean that Mosaic is the most efficient one out there?
How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function? It already exists, in the form of http://www.chromeexperiments.com/
be really really wicked slow.
I'm still astounded by how unstable and slow Google's G1 browser is. It's the main reason I haven't looked at Chrome yet.
Maybe we're getting the causation reversed. The slower the browser, the more popular it is.
Do the words "TraceMonkey" mean anything to the authors? It's the core Javascript engine of the upcoming revision of Firefox. And it is fast. Some benchmarks suggest that it is highly competitive with V8 (Chrome) and SquirrelFish (Safari).
(Speaking of which, isn't it a bit disingenous to compare Safari 4 BETA to the current version of Firefox? Why not compare the Firefox beta then? Smells of yeller-bellied journalism to me.)
Javascript is currently a hugely competitive area. Every browser revision is trying to boost performance. (Including Microsoft.) It only makes sense that the older and cruftier engines would have a harder time competing with the newer and more nimble engines created by these upstart competitors. However, with the exception of Microsoft who's stuck updating JScript (haha, bundle FAIL!), all the other competitors can and are swapping out engines for faster and faster performance.
Javascript + Nintendo DSi = DSiCade
If you look at it from a popular/performance perspective, you are going to find that, generally, the newer software is better performing, because that is a selling point above the competition. It will also be the least popular because it is newer.
"When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
How about this possibility?
"Sucky non-standards-compliant browsers aren't popular"
I'm not saying this is the case, but any decent software developer can write a web browser that's really fast. Getting it to actually render the right stuff all the time takes a lot more work, error checking, and additional code. That's going to slow things down.
Features create popularity, and popularity pushes for more features as users cry that the next browser over has something it doesn't. This create bloat.
Then again, over time, isn't this what happens with almost all software? They get more and more features as time goes by, and get bigger and consume more resources. Look at the size/requirements of any linux distro with a graphical system over the past 10 years.
No one wants to lose features, and users complain too much, so the only way to get a faster thing with less features is to fork it, or start anew (which is what the lesser popular browsers have often done).
Tibbon
tibbon.com
Either:
1) up and coming browser makers see speed as an easy differentiating factor and target their browser for it; or
2) Newer products tend to be faster since they have the older ones to compare to. And newer products also are "up and coming" and thus have lower uptake than "old and entrenched" ones. or;
3) the public puts very little value on browser speed. Those spending their resources optimizing for it rather than other features get few users as a result.
Trust the Computer. The Computer is your friend.
this really is a case of correlation not implying causation. Otherwise firefox's market share would have decreased from v2 to 3, and will decrease again when 3.5 is released.
Sure, it's a "fact", but I'll bet that in 5 years time this won't be the case. This "tidbit" does not allow us to make sensible predictions about the future of browsers.
...with actors.
Some of the ones where they had the graphics/colors rolling around:
CPU Usage: 96% Xorg, 2% Firefox.
I've seen that happen on several other sites that have javascript doing funny things with the colors/images. Makes the entire machine/interface hard to use.
I keep seeing reviews of how fast a browser is/isn't. Am I the only one that really doesn't care? All Browsers render faster than I can read the page anyway. I care about the way the browser looks/feels/renders/features. Am I missing something?
You know when you try to use Google Reader and Google Mail and Google Anything on your browser with a poor Javascript engine (even the good ones occasionally fail), it sometimes blows up?
Yeah, the Google Web Toolkit (which I believe they are all using for a front end) basically produces code that produces one metric ton of Javascript and HTML that gets dumped on the client's browser. It's not just an application, it's a whole library of Java APIs that produces a ton of Javascript that could become the de facto standard one day. I'm betting it won't but I've asked why more sites aren't using it on Slashdot before.
At least Google eats their own dog food on a large scale.
My work here is dung.
Javascript performance still doesn't matter for most users, and power users largely have Javascript disabled or blocked. Maybe Google needs to release a killer app that relies on Javascript and has borderline performance on anything slower than Chrome.
When we're just talking about loading web pages, no one is yet within shouting distance of FF with a good Adblock filter list.
JS benchmarks seem somewhat pointless for now. 99% of what we do on the web happens instantly (if you have a low latency connection) on all browsers if we stop the ads from loading.
"I zero-index my hamsters" - Willtor (147206)
... with NoScript enabled.
No I'm not bashing, I just went to the website with NoScript enabled and wondered why the benchmark didn't work for a sec...hehehe
Then I, and many others will probably never use said app.
By the way, have any of you guys tried the "basic HTML" version of GMail? I actually find it to be quite nice and I greatly prefer it over the default JavaScript version.
It's so unfortunate that researchers these days don't realize that correlation can easily be a coincidence, and not a real relationship between two variables. It is especially unsuited in this case given the tiny number of data points and, oh, the convolution of these results with other factors like OS bundling (Windows/IE) and time on market (All 3, most significantly Chrome).
A more interesting (and likely actually related) set of data would be browser performance vs. market growth rate. Where are those numbers?
Also, web developers don't curse IE because it's slow. In fact, many pages are still static and don't feature nifty DHTML tricks, so the slowness of IE has no effect on the page at all. We web developers curse IE because it's not standards compliant and because making both the CSS and those nifty DHTML tricks WORK in IE is like eating barbed wire. Firefox has acceptable Javascript performance and is mostly standards compliant, and the existence of the Firebug plugin makes it invaluable as a web developer's test browser. I don't think web developers will curse a browser like Firefox for slow Javascript performance like we curse IE for violating all the standards.
These guys are idiots.
It's obvious that the last letter in the name being a vowel has more to do with performance than popularity.
from low to high performance - a,e,i,o,u
The science behind this seems questionable at best... especially seeing how IE isn't popular so much as just saturated throughout the market.
The musings of just another geek and his junk.
Correlation != Causation
Done and done.
By that definition, if Firefox would limit network traffic to a mere 28kbps it would be on top. And RMS would browse the web faster then anyone.
What's so special about FutureMark(C)'s software? Or is it their advertising budget which desserves attention? I hope they really had to pay for their full-page ad here on /.
"How long until Google comes out with a JavaScript intensive application that will practically require Chrome to function?"
Ans: never
because 80-90% of the market will choose not to
bother with that application because they don't
know how to DAU-EN-LODE and install a different
browser.
Try this, Firefox users.
Here's a way to speed up your Firefox and make it MUCH MUCH faster.
1. Type "about:config" into the address bar and hit enter.
2. In the filter field, find and alter the entries as follows:
Set "network.http.pipelining" to "true"
Set "network.http.proxy.pipelining" to "true"
Set "network.http.pipelining.maxrequests" to some number like 30. This means it will make 30 requests at once.
3. Lastly right-click anywhere and select New-> Integer. Name it "nglayout.initialpaint.delay" and set its value to "0". This value is the amount of time the browser waits before it acts on information it receives.
Enjoy!
because 80-90% of the market will choose not to bother with that application because they don't know how to DAU-EN-LODE and install a different browser.
In that case, Google will just email their browser install file to them, because 80-90% of those people will be more than happy to click on anything in an email.
If I have been able to see further than others, it is because I bought a pair of binoculars.
There's a lot of other factors in play to help determine browser marketshare. Among them:
1) Bundling with OS
2) Feature completeness
3) Product maturity
4) Cost
I think when you look at these, it helps explain why browsers are popular or not.
Opera: Fast, Lots of features, lots of maturity, but not bundled with OS, for a long time was not free, and thus not widely adopted.
Chrome: Fast, few features, not mature, not bundled with OS, Free. Yet still managed to grab 1% of marketshare almost instantly because of Google's ability to communicate the value of its innovations, its intentions with the project, and Google's overall good reputation with consumers.
Firefox: Fast-ish, lots of features, bloating as it matures, not bundled with Windows, but comes bundled with many Linux distros, free. Built up marketshare to where it is today through long, gradual, incremental struggle, FOSS activism, discontent with Microsoft IE, and word of mouth.
IE: Bundled with OS. Managed to obtain marketshare due to anti-competitive behaviors that put Netscape out of business, proceeded then to basically cease development and ignore its many faults until Mozilla and other projects finally caught up. Was really a lot more vulnerable to competition than anyone would have ever thought, because Microsoft over-reliance on OS integration, bundling, and pricing out the non-free competition. Once a good, Free alternative was available, IE started losing marketshare steadily, and will continue to do so.
Safari: Bundled with OS. Market penetration on Apple platform is basically 100%, although many Mac users may prefer to use Firefox or another Mozilla product such as Seamonkey or Camino. But Apple's platform represents a small minority of overall web browser market. Availability on Windows hasn't made much of a difference, as it doesn't offer anything compelling that puts it ahead of Firefox or Opera, and is mainly useful for web developers and iPhone developers to test with.
It's also worth noting that speed of rendering is not all that high on my list. Speed of resolving DNS, speed of resolving URLs, downloading resources makes more of a difference to me than speed of rendering. But the main features I value in a browser are that it is capable of working with web sites I want to use (and embracing open standards to get there is important to this end), and that it has all the features I want, and is exensible so that I can add features that I come up with.
Next most important would be security, although if I really thought of it I'd probably put that ahead or on equal footing with features and interoperability.
Speed and lightweight footprint are about dead last, although if they're not fast and lightweight enough, I'll complain about it, I probably wouldn't switch from Firefox unless they released something that was an unmitigated disaster on these two criteria.
To put it into perspective, I used to connect to BBSes on a 2400 baud modem back in the day, and could read text almost as fast as I could download it over a telnet session. That's about my limit for "too slow". If a graphical and script-heavy page feels slower than plain txt @2400 bps, that's a problem. For the most part, rendering takes a small fraction of a second and isn't a huge inconvenience. In fact, I almost find Chrome's speed of scrolling to be jarring.
You see? You see? Your stupid minds! Stupid! Stupid!
Apparently, NoScript is the fastest browser available.
This just in: People don't choose their browser based on Javascript performance alone.
I went to eat some animal crackers and the box said, "Do not eat if seal is broken." I opened the box and sure enough..
Managed to obtain marketshare due to anti-competitive behaviors that put Netscape out of busines
IE was better than Netscape, and, Apache did more to kill Netscape than Microsoft did. Netscape's money business was going to be selling expensive web servers to enterprises, and Apache gave one away for free.
This is my sig.
I wonder where the choice of rendering engine enters this discussion. I love Firefox but it is a tad heavy with the addons I use. Even before I start to install addons a bare Firefox profile does not feel as snappy as I believe it should. As much as I can't really adapt to Opera as my full-time browser it does feel snappier even when loading adverts etc than Firefox when blocking them. I have heard WebKit is a snappy rendering engine, Konquerer and Safari both seem to match that appraisal, so I wonder what Firefox would perform like if it were using WebKit instead of Gecko. I heard ages ago of a project that was aimed at doing just that, but ain't heard anything since; anyone know if it stalled?
If the web was really going to focus on "performance" the W3C should start working on a tag. Thus alleviating the browser from munging though all that text and then compiling.
I've heard a lot of talk about Javascript performance as intensive Dynamic HTML applications become mainstream.
Most of the apps I seen really don't have that much Javascript when you compare it to the amount of code that is in your typical desktop app or server side application. And ultimately many of the functions are small.
What I've noticed is instead their is a difference in the rendering engine itself. Javascript might be a single line to change the CSS of an element or change the visibility attribute, but then the browser takes forever to collapse the item...or the CPU spikes when some huge element of a big page disappears and the whole page has to move over/up/down.
Are we really talking about how fast the DHTML engine responds or is Javascript really that stinky slow that changing the element underlying take a while. I'm not sure I care if calculating primes in JS could made faster. Isn't most of Javascript just mapping down to a C++ library below it?
I ran Peacekeeper with both Firefox 3.5 and Safari 4 on my iMac. Safari was 3 times faster.
But, Safari does not have the add-ons that Firefox does.
So, Firefox is the only way to go for me.
Dave Barnes 9 breweries within walking distance of my house
The linked article seems to be quite devoid of propercontent ... after a test of some browsers on just one computer (and, I guess, just one OS) they deem that there is an inverse correlation between popularity among the people visiting their site and performance.
Not quite what I would call an accurate and scientific approach!
This being said, there might be a grain of truth in the very fact that the more popular the browser the more "corner cases" are exercised (and thus have to be implemented). By corner cases, I do not mean what the standard dictates, but what you find (ab)used on way too many pages.
I like it way more than the JavaScript one. At least on basic HTML I can choose where to open an email, at the JavaScript I'm forced to open within the same window.
Now, I can't stand any of gmail user interfaces (also, I don't like to trust all my mails to it), that is why I use POP.
Rethinking email
Like slashdot, you mean???
Assuming this correlation means anything, which it may not, it's more likely to be this:
The less popular your browser is, the better/faster it has to be to compete.
If there are two sites and the one requires me
to first click on something and install it,
and the other JUST WORKS and I DON'T HAVE TO THINK ABOUT A SINGLE THING to make it work, then your market is not going to want to bother with the former. Have you ever dealt with a large number of end users? Obviously not. Most people have already spent an evening figuring out the LABORIOUS COMPLEKSITY of installing flash which has more than enough power to run any kind of app that you might want to do in Java Script. Get real.
I'd use a desktop application.
Google Chrome Installer extracts into C:\DOCUMENTS and SETTINGS..\ so I tried running it as a portable app. Runs ok, now how do I get Flash onto the device. There is a reference to flashplayer-win.xpi, but when I try and extract it, I get corrupt zip file ..
I wouldn't need noscript and an adblocker if the advertisers weren't such annoying fucks with their dynamic scripts that freeze the page while they load and run, and their talking flash adverts that freeze the page while they take ages to download.
davecb5620@gmail.com
when it finally starts. I am able to start IE and Chrome and browse to the page in both in the time it takes FF to grace me with it's presence. Just yesterday FF was ejected as my default browser. It may have a faster javascript engine, but who cares if I have to wait 40 seconds for the dog to load.
You are unique, just like everyone else.
It seems to run all right, but I'm still typing this on Firefox because Adblock trumps Chrome/Iron's performance & user interface design advantages.
Look closer next time. Adblock is part of Iron. Take 15 seconds to download and install the ad block list from their News page:
News
12.03.2009: New Iron-Release: 2.0.168.0
Today we release a new Iron based on Chromium 2.0.168.0. There were updates to Webkit and the Javascript Engine V8, so the new Iron version should be significant faster. Additionally we improved the the adblocker.
14.12.2008: New Iron-Release: 1.0.155.0
After Chrome 1.0 is released, you can surely download a new Iron, too. We have also updated the adbock.ini is,which you can get here. Further we have improved the Portable Version, it now accepts parameters such as -- incognito, to start Iron immediately to the "anonymous mode".
... because the script that runs the referenced test ran so slowly in Seamonkey that it stalled out entirely.
This isn't unusual... hie yourself to realtor.com and watch it in -- uh, inaction any time you like.
~REZ~ #43301. Who'd fake being me anyway?
Actually parent is not troll. Most sites don't really need Javascript unless you use IE where it is used for tweaking. So you can surf the web just fine without it most of the time. Unless you are a fan of XMLHttpRequest and friends of course.
Quick way to get 30% Funny 70% Troll: defend Opera browser on
Google's services will have to be reliable first.
This is a shame that firefox 3.5, at least on Ubuntu has tracemonkey turned off by default. I am developing really heavy web application right now (Dojo on client-side), and I was amazed how it's performance changed when turned tracemonkey on.
Now, just how can I explain my client to use recent FF or Chrome? ;)
comes to internet exploder, the term "popular" should be changed instead to "pervasive". To me, "popular" conveys a sense of attraction/interest/liking by the USERS or CHOOSER, such as choosing a car, camera, phone, debutante, model, etc. Developers and laziness and intertia in developemnt circles, and the damned GAMES msoft played to kill Netscape and others off made mshaft pervasive, but by NO means is that set of warze "popular" as in liked. If i have a say, the wand would be waved, and exploder gone "poof". But, fortunately, i don't have to be the axeman. msoft is doing it to itself.
Previously: "Linux... Toward the Sunrise..." Now: "Linux... Toward the-- No, now, part of Every Sunrise"
A precompiled solution would be interesting, but it requires a standard for the bytecode. While there seems to be a move toward bytecode compilation in the new crop of JavaScript engines, actually getting them to agree on a standard for this will be difficult.
If you can get that done, though, then there's no need for a new tag. Just add it as a possible MIME type ("application/ecmascript-bytecode" perhaps?) on the script tag.
Opera is not famous..but its fairly slow when compared to Fireox.
Hey, I forsee a time when HTML will be regarded as a "legacy" markup, only to be accessed by a special extension.
We're almost at that stage now. It often seems to me that the only real reason for all that dynamic and so-called "Web 2.0" content is to deliver more bandwidth-intensive advertising. Maybe it's time to take a step back and have a Campaign For Real HTML.
There are an whole slew of browser attacks which occur via JavaScript, Flash or Acrobat, and NoScript is extremely effective at stopping these.
That's it's role.
An side effect is that some ads are rendered less obtrusive.
However, for blocking ads, you're best off grabbing Adblock and subscribing to the relevent filterlists.
How is Google's javascript engine in terms of loose coupling? Mozilla uses a javascript engine called SpiderMonkey which has all sorts of uses beyond web browsers. In fact, it's a really really good way to use JavaScript as a language for application extension/scripting. (Forget what you know about "JavaScript sucks" ... the things you hate are all browser/DOM related; the language itself is elegant and beautiful.) I'd hate to see this nice piece of embeddable code fall into disrepair.
Tired of FB/Google censorship? Visit UNCENSORED!
Bo-o-o-o-gus.
This "study" didn't measure browser speed at all. It compared only the speeds of the javascripts that the browsers use. TFA says so fairly clearly.
If you're making heavy use of sites that are mostly javascript, this is a useful study. For the rest of us, it's yet another case of measuring a tiny corner of what is claimed, and then asserting that this measures the whole thing.
Using similar reasoning, we can imagine an oceanographer measuring the parts of the ocean along the beaches where most people are found, and concluding that the oceans average about 2 meters deep. (There's gotta be a good auto analogy here, too.)
As someone else has pointed out, most "power users" of browsers mostly disable java and javascript (and Active-X and any other misfeature that lets strangers run code on their machines). They may use NoScript with FF and enable JS for selected sites. Or they may simply copy the links to another browser such as opera or safari when they want to use JS. So to them, firefox and mozilla may well be the fastest browsers, since they permit easy selective disabling of all scripting features.
And we should also note that the time to render most web pages is mostly the download time. If due to network delays it takes 23 seconds to download a page, and browser X renders it in .001 sec while browser Y renders it in .01 sec, there's no practical meaning to a claim that Y renders 10 times faster than X. If the page takes 23.001 sec to render in X, and 23.01 sec in Y, few people will be able to reliably tell you which is faster.
If this were announced as a comparison of various JS interpret speeds, I'd take it seriously. But claiming that it's about browser speed pretty well discredits the authors (and the editor who wrote the summary).
Those who do study history are doomed to stand helplessly by while everyone else repeats it.
It's called feature creep/bloat. Unfortunately, it seems a necessary evil of life or 'the nature of the beast'
I have tried it, but not for awhile.
The most obvious thing missing is: Keyboard shortcuts. I can actually navigate a lot of email in gmail without using the mouse. Can you do that with the basic HTML version?
Don't thank God, thank a doctor!
A javascript based flash replacement, including the toolchains for development that Adobe provides, and libraries that make doing things that are easy in flash just as easy in javascript. I think that would be the killer app they have in mind, and have either already created, are creating, or are depending on the OSS community to create.
...
I'm not even slightly surprised, FireFox runs like crap under Mac OS X. Safari is soo much faster
The Christian religion has been and still is the principal enemy of moral progress in the world. -- Bertrand Russell
Really? Seems like at least 25% of computer users know how to install another browser.
Note that this demographic includes Firefox, Opera, Chrome, and pretty much all non-IE and non-Safari browsers.
I've been racking my brain on creating the next browser to kill Mozilla, Safari, Chrome and IE.
I am not a professional programmer by any means but I think I have the world's fastest browser. I admit it is not HTML 1.0 compliant yet and must worn it doesn't do very much yet. It is able to access the 'World' of computing which is what we expect of any browser. I am going to upload it onto Sourceforge real soon after I add some extra code. I need to work on the architecture a bit and I have yet to make any substantial flowcharts.
Smoke signals here... I win!!
"All great wisdom is contained in .signature files"
I prefer FF because of all it's great addons but, generally it's been getting slower and slower. But then so has my whole machine and I doubt FF is the sole cause of that. I have 5 simple tabs open and FF (latest version) is hogging memory at 197,000K It's second in task man right after Visual Studio at 206,000K.
Ug. One of these days I should find out which addons are contributing most to this glut.
There are the JS-heavy sites my sibling discusses, and usually the slow part of a browser isn't in the delivering the result to the screen - so you have to wait before you can even start to read (Firefox). And browsers that render slowly can also be painful to use, as that can make things like scrolling (Safari) and animation (IE) jerky. And then there is the energy consumption angle. Time your browser is crunching JavaScript cannot be spent idling. This can matter a lot for embedded devices and suchlike.
Well, that may be your definition of popular, but let's see what Meriam-Webster has to say about the defition:
1: of or relating to the general public
2: suitable to the majority: as
a: adapted to or indicative of the understanding and taste of the majority
b: suited to the means of the majority : inexpensive
3: frequently encountered or widely accepted
4: commonly liked or approved
So defs 1, 2,3 are all pretty correctly describing IE. So really you have a problem with 4 being applied to IE.
Sounds like you may want to consider changing what you think "popular" means to you.
"But this one goes to 11!"
if firefox didn't have any features it would be as fast as chrome.
chrome doesn't even have a context search...
No, this isn't poor programming. There are so many configuration options that to build menus for them all would take too much time. Also, they don't/can't anticipate all the reasons why someone would want to configure at thing. Where should the setting be? Also extensions may depend on being able to depend on a config option being set a certain way and may set the setting themselves. If another extension resets it then those two extensions are incompatible with each other, but if there is a menu driven way to set all these settings then ANY EXTENSION THAT WANTS TO SET ONE must account for the possibility that the user might use the menu to change the setting. editing about:config 'voids your warranty' so if you do so, you might break stuff like extensions you have installed. Having the void your warranty screen makes it possible for extensions to set things and reasonably count on them remaining set.
...
Should we feel left out , or just sit back and watch the cat fight?
Chrome vs IE vs FF is way down the list from "which Catsup(Ketchup) to use.
Next!
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
Right.
1. How do you explain that IE8 is the youngest of the non-beta's and the slowest.
2. Why is it then that IE has more problems with standards? Does it check so much for broken html/css/javascript it can't even deal with standard compliant code? Oh and then explain how a trailing , in javascript FAILS under IE but not firefox.
3. So, IE8 has more features then firefox...
Something tells me you don't know what the hell you are talking about. Did you ever actually use any other browser then the one that came with your Dell?
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
I might care, if I didn't have to deal with a client who won't even update to IE7 at gunpoint.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
Paraphrase it as "The more popular the app, the less effort developers put into coding" and it suddently makes a lot of sense.
We long know that many users base their "preferences" on something different than quality.
IE users simply don't have preferences... whatever you give them they'll chew & perhaps choke on.
FF users are obsessed with the free/open source or anti-MS movement, makes you instantly geek.
As for the test, it would be good to have one on rendering speeds. After all scripting is of no use if you don't render the page. And that's much more computationally intensive!
will web developers start cursing Firefox?
I already curse Firefox: slow, unreliable, too many irritating quirks. I've probably made things worse by installing too many dodgy plugins, but I think it's mostly the fact that its rendering engine is a bloated kludge. Seems to be designed more as a platform for XUL apps than as an efficient, reliable renderer.
I have issues with Chrome too (mainly that they expect me to relearn all my GUI idioms pretty much from scratch). But all in all, it's a much sounder product. Once Chrome's plugin ecosystem reaches critical mass, I'm gone.
Yeah, I know, plugins will probably introduce problems into Chrome as well. I'm counting on Chrome's API designers to to a better job of insulating me from plugin screwups. We'll see.
--What say you now?--
security risk - At least it's blocked externally but not internally where I work. Telnetting into Cisco PIX seems to be easier than using their web based way in.
Gopher, checking in....
You use a lot of of CAPS randomly.
I suspect you're in the 80% of people that would click on paris_hilton_nude.exe if you got it in an email.
I like the idea of their url bar, but its slow and freezes my machine before it has loaded some components into memory
If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
http://xkcd.com/$(RANDOM % 500)/
I don't therefore I'm not.
Unfortunately, the benchmark doesn't publish its code, and tries very hard to prevent anyone else getting their hands on it. I spent a day or so trying to reverse-engineer their obfuscation once before I gave up. Furthermore, nowhere is there an explanation of where the number the benchmark shows actually comes from.
This immediately drops its credibility compared to benchmarks like v8, sunspider, dromaeo, or anyone else who publishes their methodology for public review. It turns out that it's pretty easy to mis-write your benchmark in such a way that its results are useless (e.g. stopping a timer before the work you're benchmarking has actually been done in a browser that does it lazily)...
Why? Well because it's about 80% a test of the underlying system (Ram, CPU, Video card etc) I ran it myself by doing a pretty simple check (removing 75% of the ram going from 2G to .5G) and the performance diff was huge. In short. They spend too much time testing the performance of the Hardware and too little testing the browser against itself.
I'm sorry, I'm to tired to be witty at the moment so this message will have to do.
This article is absolutely absurd. It's pretty terrible that data are being misused like this. This is a classic example of correlation and causation. Assuming that everything they say about the data they collected it true, it doesn't mean that when browsers become popular that their quality decreases. It just means that popular browsers and low quality browsers are related... not that one causes the other. For example, murder rates and ice cream sales are highly related (they are, look it up), does that mean when someone sells more icecream that people die? No, it just means they they're highly correlated. Also, another flaw in this terrible article is that people are self selected to their website. It could just mean that more people who use IE visit their website for whatever reason.
Carl Sagan quotes get you an automatic +5 on all posts.
I'll start using Chrome when it's completely free software (note that I'm saying this because I honestly don't know what license it is), and when it's buildable and runnable on GNU/Linux. Until that day, it's just out of the question.
Seems like it's only slightly faster than Safari 3.2.2...so much for TraceMonkey.
Don't toke and post.
Take it from me, I used to do it myself. Thought I was being all brilliant and persuasive until next day when I realized my posts all looked like your abomination up there.
After using Chrome for several weeks at work, I switched back to Firefox. The difference is Ad-Block Plus. Not loading the adds far exceeds any performance gains from other sources.
Yeh just like FutureMark products. Being the most popular benchmark software, it is the slowest as well.
Ahhh. So in order to make the most popular browser, it has to be the slowest! Finally, the solution is there.
Did an analysis of the figures, mostly because there was none to be found. There's actually a pretty striking exponential relationship between speed and adoption. Here's a graph:
http://2.bp.blogspot.com/_lhmAHZ1VwRE/Sg2k-WLthEI/AAAAAAAAACk/iub7fBGjcfQ/s1600-h/results.png
GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
Hi All.
:-((
Check out this new research: speed compare of different browser plugin technologies. (the speed demo also include java script) www.3djam.com/speed_demo.aspx (note that source code is availeble for review)
This demo is a good way to compare different programming technologies for browser client based applications.
Just as with the browsers the most popular (javascript and Flash) are the slowest solutions.
When you try the demo then try to run the same plugin in different browsers (e.g. javascript and Flash) then you will see that even with plugins speed are quite different under different browsers.
Please also note that Roozz plugin is very different from the other plugins. As it run the embedded application in a seperate process, thus speed of Roozz applications are not affected by what browser you use.
List is here: http://en.wikipedia.org/wiki/List_of_web_browsers#Gecko-_and_WebKit-based_browsers
Nothing that works in Windows, though...