Slashdot Mirror
Firefox 3.5 Hits Release Candidate Milestone
macupdate writes "Firefox 3.5rc1 has started trickling to users (mirrors and appropriate pages should all be updated soon). You can read the release notes. RC1 still scores a 93/100 on the Acid3 test."
Beta 99
There are two kinds of people: 1) those who start arrays with one and 1) those who start them with zero.
To be fair, Chrome is from Google. It's going to be beta for another three years.
I still don't understand the obsession with Acid tests - they measure performance in incredibly obscure areas and have a comparatively small bearing on real world performance. Webkit and Opera in particular have designed to the test to an extent, resulting in good scores but not necessarily comparable general compliance. I'm also slightly confused by the use of the word "still" - none of these bugs are severe enough to risk breakage leading up to a release candidate. I believe far more relevant are performance, bug fixes, features and HTML5/CSS3 support (which make far more of a contribution to moving the web on that Acid Test scores do) - areas in which Firefox 3.5 has improved dramatically. Talk about focusing on the negatives...
Yes, even slower than IE8. From start up times to rendering pages firefox is by far the slowest. If you don't believe me download IE8, use it for a week, and you'll see for yourself. IE8 sucks for other reasons (crashes more, no plugins, forgets log-ins), and firefox is my main browser, but it is seriously falling behind. It's speed, private browsing, and I would argue even security (no sandbox/protected mode) are subpar compared to the competition. And they really need to fix private browsing, it's pretty sad when an IE feature works better than the open source alternative. As repeated ad-nauseum here firefox is still my main browser due to plugins, but everytime the browser freezes because one tab decides it wants to do something I re-evaluate this decision.
yet don't work 100% in real world webpages. Standards compliant be damned if you can't render real pages.
Paying taxes to buy civilization is like paying a hooker to buy love.
I wish Mozilla would make up their minds: are they going to target the Corps or not?
Even if you can get an MSI from Frontmotion (http://www.frontmotion.com/Firefox/download_firefox.htm), the corps will never go for it unless it comes off the Mozilla servers and is on the same web page as the current XPI installers. It's a "warm and fuzzy" thing that they need.
If Mozilla could somehow sanction those MSIs from Frontmotion then the corps would be more comfortable with it. Even a link from here (http://www.mozilla.com/en-US/firefox/all.html) would give FrontMotion's MSI package credibility.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
Such as...? I use Safari (at home) and Konqueror (at work) nearly exclusively and haven't had problems with these mythical IE-and-Firefox-only pages.
Dewey, what part of this looks like authorities should be involved?
RC1 still scores a 93/100 on the Acid3 test.
Minefield has scored 94/100 for quite some time now, so I doubt Shiretoko will score any better at release.
I know it's a tired topic, but it's a legitimate one, and not one that can be explained away by saying "extension writers suck".
That's interesting. Which version of Konq? On 3.5.10, the Slashdot discussion system is FUBAR for a few weeks now. It was working fine, in-place replies, dynamic comment loading and all, but it stopped at some point.
This is Slashdot. Common sense is futile. You will be modded down.
Adblock Plus & NoScript work fine in Minefield, so they almost certainly will work in the RC. I don't know about other plugins, though.
Every WebKit browser should be getting 100/100.
GENERATION 25: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
4.2.something. The only problem I have is that /. changed their CSS in the last couple of days so that now the message header sometimes fills the whole screen and pushes the message text against the far right edge.
Dewey, what part of this looks like authorities should be involved?
This is actually a pre-RC build, the actual RC should be coming in the next week.
See this site for more details.
http://blog.mozilla.com/blog/2009/06/17/firefox-35-beta-users-will-receive-update-to-early-release-candidate/
Blessed are the pessimists, for they have made backups.
The amusing part is that, on my screen, your post looks exactly as you describe.
I've found the problem goes away if I increase the window width sufficiently.
I'm running Firefox 3.0.11 on Windows XP, but I see the same problem on Firefox 3.0.? on MacOS Leopard at home.
It doesn't hurt to be nice.
and Konqueror (at work)
You are the first person I have ever heard say "I use Konqueror", I didn't think anyone used it. I figured it was some throw back browser that was still included in Linux distros for nostalgic reasons. What does it do for you that Safari or FF wouldn't/doesn't do?
If you could reason with religious people, there would be no religious people
And for those who still don't get it, the correct spelling is "anticlimactic".
It's from "anticlimax".
You know what a climax is, right? This is slashdot; you've surely read about them, even experienced them by yourself.
Don't hog all my memory. Konqueror 4.x broke Slashdot and digg so I had to stop using it and use firefox instad. But now Slashdot works properly again. I can use dig but I get a regexp exhaust error if I try to login in digg. I still have to use firefox for gmail and facebook though.
Since when is H.264 industry standard?
I'm starting to think GNU is the problem with "GNU/Linux" these days.
yet don't work 100% in real world webpages. Standards compliant be damned if you can't render real pages.
What?
If the browser follows web standards 100% and yet some webpages render incorrectly - doesn't this mean the issue is with the web page and not with the browser?
Web standards exist so that we shouldn't have to answer the question of whether the web browser is designed for the web pages or whether the web pages are designed for the browser.
This seemed like a reasonable sig at the time.
H264 is industry standard since the day it was proposed/accepted. Industry standards aren't defined by nerds, they are defined by industry, huge boards of professionals and several computing specialists. There are billions (if not trillion) worth of broadcasting equipment, workflows, applications trusting to MPEG standards. Near all HD broadcasts are h264 and you should be thankful that TV industry didn't buy Microsoft's "but VC1 is documented too!" tricks.
They sit, argue, propose and after years, MPEG standards appear. H264, being part of MPEG 4 is more standard than anything you can imagine. It is result of 300 Experts discussions, several universities, companies and even governments.
Of course, it would be wise to wonder around saying "evil patents and mpeg la" but reality is a bit different. Even the reasons of patents are different than you may think.
Safari's renderer is WebKit, which is open source and based on KHTML.