The OP is saying that the way the headline is phrased makes it sound as though this is the end of the Firefox browser.
"BSD is dying" is a meme that has been floating around for years.
I haven't had any back and forth with google....It's not my script. I'm just a happy user
Try this script for Greasemonkey.
I cleared all cookies from Chrome, Opera, and FF, and went to http://www.capitalone.com/autoloans/
Chrome and Opera both gave me rates of 3.5%.
Firefox gave me 2.7%.
I proxy my FF sessions through a ssh tunnel to a personal Linux server I have, which is located in Michigan. So to see if that had an effect on it, I cleared cookies again and then disabled the proxy settings. Restarted FF and went to the URL again. This time I got a rate of 2.3%.
I went back to Opera and Chrome, deleted cookies and restarted again. Now Opera was 2.3%, and Chrome was 3.1%. Did it again, and Opera was still at 2.3%, and Chrome had dropped to 2.7%. It's as if this site is just coming up with totally random numbers.
Really, the ease of compiling packages from the Arch User Repository is what makes Arch Linux so nice. Download the tar.gz, extract, and run makepkg.
In fact the new 2.6.36-ck kernel is already in the AUR/
The anticipatory scheduler was removed from the kernel a few releases ago.
Even more ridiculous. So they not only were on the scene, but they also had their hoses out and were spraying water, just not *at* the fire.
He *did* pay his $75 fee, but they didn't do anything until the fire had actually spread to his house. I'd be pissed if I were him. They wouldn't do anything to *prevent* his house from catching fire in the first place? It doesn't take a genius to figure out that uncontrolled fires usually spread.
Asynchronous inputs are at the root of our race problems. -- D. Winker and F. Prosser