Slashdot Mirror
Mozilla Firefox 3.6 Released
Shining Celebi writes "Mozilla has released Firefox 3.6 today, which adds support for Personas, lightweight themes that can be installed without restarting the browser, and adds further performance improvements to the new Tracemonkey Javascript engine. One of the major goals of the release was to improve startup time and general UI responsiveness, especially the Awesomebar. You can read the full set of release notes here."
If you have the Switch Proxy Tool, I strongly suggest you disable it. Caused all sort of issues when upgrading. If you've already upgraded, right click on the shortcut and run in safe mode, there you can disable it. YMMV.
=================
Unix is very user friendly, it's just picky about who its friends are.
Tried on Windows, performance improvements are immediately noticeable. Wastes less screen space by default. For those who are used to the old look-and-feel can feel a little awkward at first.
Set extensions.checkCompatibility to false and you're good to go.
Firefox 3.6 does beat the newest Chrome on some Javascript benchmarks (and Chrome beats Firefox on others). I think it's safe to say they're in the same ballpark. http://www.fudzilla.com/content/view/17199/1/
Seethis for details.
Best Slashdot Co
about:config
set mousewheel.withnokey.sysnumlines to false
set mousewheel.withnokey.numlines to 3
As good as new... Wait a second.
The new tab now appears to the right of the current tab when you right click on a link and select "Open Link in New Tab."
I just discovered that after about 5 seconds of "Hey, where'd my new tab go??"
I can see the fnords!
That delay is nothing to do with your browser - that's Slashdot scanning of a bunch of ports on your IP address. I spotted this a few weeks back when I made a post to Slashdot while running a "tail -f" on my firewall logs, although I've been aware of the lag a lot longer than that. It seems that if your firewall just DROPs the packets you get a delay while it retries a couple of times, whereas if you REJECT then it's a good deal quicker. There's some caching going on as well, once you've gone through this the lag disappears for a day or two, then re-starts. As it says in my .sig - WTF?
UNIX? They're not even circumcised! Savages!
Not SMTP; HTTP. The ports scanned are all common default ports for web proxy applications like Squid's :3128, various ":8080" type combinations and such like. I'd have to go digging through my logs to get the complete list, but I'd guess there are about a dozen ports checked in total.
What's so irksome about it is that it's a straight SYN scan done very slowly that impacts any users that have a firewall that DROPs packets with an apparently inexplicable delay of several seconds. If you really feel the need to do this, which the Slashdot team obviously does, it would be much quicker and less annoying for users do the scan at a faster rate without the two or three retries currently used. Better yet, kick the scan off in the background while the data is being entered data into the form and reject the post if necessary when the "Preview" or "Submit" button is clicked. Even if a post is submitted through an open proxy before the scan completes, Slashdot's delay between posts from the same IP will ensure that only one post can get through before the ban hammer comes down.
UNIX? They're not even circumcised! Savages!
Chrome is open source in the same way that OS X is open source.
Sure they're both based on a open source project (Chromium/Webkit and Darwin/BSD) does not mean they are truly open source. Try to modify and redistribute either and see how long before either of their "parents" get all lawyer-ey.
The analogy Chrome : Chromium :: OS X : Darwin/BSD is nonsense. You can't build an almost identical replica of OS X from open-source code, or anywhere close. Chromium is fully open-source, and it's essentially identical to Chrome. It's what the Chrome developers themselves use for development and testing.
MediaWiki developer, Total War Center sysadmin