Firefox 4 Beta 8 Up 385
An anonymous reader writes "Mozilla has released a new beta of Firefox 4 this morning. Originally intended as a quick update for the feature-complete Beta 7 release, the new Beta includes 1415 bugfixes, a fine-tuned add-ons manager, improved WebGL support as well as URL bar enhancements."
The only question I have is (Score:5, Insightful)
Will the next version of Firefox (whatever version it may be) be slower? Because quite frankly, FF has become a giant turd in that respect, so much so that, although I love it, I'm considering alternatives on my lower-end machines...
Re:The only question I have is (Score:5, Informative)
http://weblogs.mozillazine.org/asa/archives/2010/10/are_we_fast_yet.html [mozillazine.org]
That benchmark is a bit old (two months ago), but you get the idea.
Re: (Score:2)
http://weblogs.mozillazine.org/asa/archives/2010/10/are_we_fast_yet.html [mozillazine.org]
That benchmark is a bit old (two months ago), but you get the idea.
Funny, I initially misread the article title as "Firefox 4 Beat 8 Up", which could be true if that trend line continued for the past two months. ("8" meaning Chrome v8.) Browser deathmatch!!
Re:The only question I have is (Score:5, Insightful)
There's more to a browser than rendering and Javascript performance. Firefox has become a hard disk hog. It almost continually writes to disk, which can be very slow, for example on netbooks with first generation SSDs or when you keep your profile on a USB stick (portable Firefox). Worst of all, when it does write to disk, the whole browser locks up. It's barely usable on netbooks for that single reason. You'd think that nothing a browser does could justify writing or reading megabytes of data almost every minute. That's still what happens. (No, extensions or plugins are not involved.)
Re:The only question I have is (Score:4, Informative)
Unfortunately setting up a ramdrive is above the general public's scope of ability.
Re: (Score:3)
There's more to a browser than rendering and Javascript performance. Firefox has become a hard disk hog. It almost continually writes to disk, which can be very slow
Isn't that because they moved to using sqlite to store bookmarks because NTFS used to eat your entire bookmarks file if Windows crashed? Whereas sqlite syncs multiple times every time you update the database?
Re:The only question I have is (Score:5, Interesting)
NTFS is a journaling file system. It is unlikely that a system crash would cause data loss on anything that has already been written to disk.
Perhaps you should tell that to the many, many, many people Cc-ed on the infamous 'Windows crashed and ate my bookmarks' Mozilla bug.
And yes, it happened to me several times: any time XP blue-screened with Firefox running I'd find my bookmarks had gone after the reboot.
Re:The only question I have is (Score:4, Insightful)
Then why doesn't it happen with other browsers?
IE writes to individual files per bookmark, whereas Firefox used to write to one big flat text file which could be several megabytes in size. Chrome presumably learned from Firefox and writes to some kind of database?
Also, any database Firefox might be using it still going to be sitting on top of NTFS and thus prone to the same problem if it really is the fault of the file system.
Sqlite syncs three times every time you update the database, and uses its own journaliing to allow it to recover from corruption.
Sounds more like a bug in Firefox than one with NTFS.
Then why didn't it happen on other file systems? It happened to me often enough that I switched that partition to FAT32 in the end, which could recover from a crash without randomly deleting files.
In the real world it's an interaction between how Firefox was updating its bookmarks file with poor design on Microsoft's part. Firefox would be writing the file numerous times while you were browsing the web, and somehow NTFS would truncate the file to zero bytes if it crashed at the wrong time during that process.
And I'd also add that one time I had NTFS delete a _two gigabyte_ file that I was downloading from the Internet when the power went out. I suspect the problem is somehow related to files which have been created but not closed when the operating system crashes.
Re:The only question I have is (Score:4, Interesting)
After reading your post I did a very quick test in .NET using System.IO.File.Open :
Repeating the test with a FAT32 filesystem, I had the following results :
So, my tests showed the same results... I then tried System.IO.File.AppendAllText to append large amounts of data to an existing text file and deliberately crashing it before it finished.
Under NTFS, the file was zeroed. Under FAT32, the file contained the original data plus part of what I was writing (I assume up to the point that it had written when I crashed it).
Note that I can't say if this is a fair test since I don't know what underlying stuff .NET is actually calling, but it's the only dev environment I have on my Windows system (which is my work box)). However this test definitely shows a difference between NTFS and FAT32 in some circumstances. Not where I first expected, but definitely somewhere...
Perhaps it'd be fair to blame both NTFS *and* Firefox for this one - Mozilla could have found a better way to write the data after all (which they eventually did by switching to a database, but I get the feeling they could've achieved it more simply in a minor update beforehand)
Re:The only question I have is (Score:5, Informative)
You may wish to re-try this on FF 4. There has been significant work put in to reducing disk access in Firefox:
There is also a tracking bug [mozilla.org] for bad I/O patterns available, so you can see what they're up to.
Re: (Score:2)
There's more to a browser than rendering and Javascript performance. Firefox has become a hard disk hog. It almost continually writes to disk, which can be very slow, for example on netbooks with first generation SSDs or when you keep your profile on a USB stick (portable Firefox).
You can disable the disk cache, that would help in situations where the disk is slow. It's disabled in Mobile Firefox, for example.
Desktop Firefox is tuned for typical desktop/laptop machines, where it makes sense to cache on disk quite a bit. I think you raise a very good point, as netbooks are getting more popular, Firefox should be tuned for them as well.
Re: (Score:2)
There are somewhat more recent graphs at arewefastyet.com, although only up to Nov 4th.
Re: (Score:3)
Re: (Score:2, Informative)
Javascript is not the problem, it's the interface. (Score:2)
Take a page from opera's (11) book, I can be loading my default 20 tabs all at once and the interface is still responsive.
Firefox, good luck, the entire browser chugs to a grinding halt for 10 seconds, then the next 10 seconds it's hitchy but at least responsive.
This is on a quad-core machine running at 3.5ghz. Chrome maxes out all of my cores to 100% and is done rendering in about 4 seconds, AND it's rendering all the ads that are being blocked by adblock. Firefox never uses more than 30%. Bad programming.
Re: (Score:2)
This is not the interface, it's the SQLite database. Every time you access a page, it has to write to the database.
It doesn't _have_ to write to the database, it chooses to write to the database. I believe it's updating things like the time you last visited the page, which I totally don't care about.
Re: (Score:2)
It is in fact faster or as fast as chrome in version 4 from a javascript perspective, and it has always run on less ram. So it should be much snappier now.
I Beg to Differ
My desktop [photobucket.com]
There is a reason people have been calling FF bloated lately. This is without any addons, plugins (besides maybe Java), or themes or any crap built into FF. This is a fresh install.
Sure, FF may be working on good Javascripting engines, I haven't looked at the benchmarks recently, but the claim "It runs on Less Ram" died a long time ago.
Re: (Score:2, Interesting)
There is a reason people have been calling FF bloated lately. This is without any addons, plugins (besides maybe Java), or themes or any crap built into FF.
34.7 megs? I can only run 120 FF processes on my main desktop then. Bummer. Hmm, that would be 12 across and 10 down.
Only things that matters to me are:
Adblock plus
Firefox sync
firebug
flashblock
ghostery
remove-it-permanently
Noscript
once I can get all that cross platform, I'm ready to switch. I'll put up with anything else, as long as those addons work.
Re: (Score:2)
Oh don't get me wrong, there's plenty of reasons to use Firefox and you've compiled a nice list.
Thing is people are claiming it's this much slimmer streamlined browser, like something really lightweight. If you've got a decent computer you obviously won't have any problems running Firefox as a regular browser.
However, there are people who will set up their Dual Monitors, and they'll want to have Crysis on highest settings on One monitor while a Youtube video plays their favourite song on the other with MSN
Re: (Score:2)
Lightweight! I've got Firefox/Firebug open to a single tab (granted, a lot of refreshing and ajaxing) and it has 3:52 of CPU time and is using 206MB of RAM and 202MB of VM. Ha!
Re: (Score:2)
comparing things like this is totally unfair and lying to yourself
I closed the IE process. Killed Process tree. Terminated, wasn't listed. Then I opened 1 IE browser, navigated to this article. Then I opened Firefox, navigated to this article.
It may be unfair that Firefox can't get its components built into the operating system - but the fact of the matter remains that IE, it's two processes combined, one likely handling the browser application and the other one handling the tab (You'll notice that opening a new tab creates a new IE Process) - those two combined still did
Re: (Score:2)
Re: (Score:3)
> And yet if I open Firefox it takes nearly 30 - 45 seconds, while Chrome opens almost
> instantly.
I assume that's with a clean profile (or at least one without extensions) and that you're using the Firefox 4 beta, right?
On Windows Vista/7, there are some existing dwrite issues being worked through where trying to initialize the dwrite library will go and read all the fonts on your operating system in their entirety; issues that are partially fixed if you install the updates IE9 requires and partially
Re: (Score:2)
Yeah, I've been using Beta 7 for a while and for whatever odd reason, I've been getting momentary freezes as it's doing routine stuff. Is this happening to anyone else, or just my specific configuration?
Re:The only question I have is (Score:5, Informative)
It has been a turd since this summer, mostly due to the bug in the SQL code which
killed interactive performance. It was repaired this week and should make beta9. It
is also in recent 3.6 builds so mainline firefox is almost unbearable.
Meaningless javascript benchmarks are not very useful for this sort of bug- which
gives 10 second hangs when working with history or bookmarks.
Bug number 595530
Re: (Score:2)
the AC is a moron who can't be bothered to read a bug report before mouthing off.
Re:The only question I have is (Score:5, Funny)
Given the burden of the many ad-ons I run, I'm not sure which is fucking up, the browser or the add-ons.
One nice thing about running 8GB RAM on a 32-bit system with PAE enabled is that when FF gobbles memory it maxes out at 4GB!
I'll keep it for the add-ons. RAM is cheap.
Re: (Score:2)
My experience with Firefox 4 beta says no! I've been running it on my laptop for a few weeks and it's far faster AND more stable than 3.6
Re: (Score:2)
FF, and especially FF4 are very fast for me on Macbook. As fast as Chrome for all intents and purposes. Of course that's not scientific, but then there do exist some benchmarks and you can look them up yourself.
Re: (Score:2)
I run Chrome, Safari, Opera, and IE up to 8. (No Win7 to run IE9 on.) At times I run them all on the same websites during web design. IE is the champion dog. No question about that. The rest? In actual use? Indistinguishable.
Except that with Firefox I have Adblock and Noscript, so way less crap
I like it (Score:3)
Looking forward to getting this update, my beta 7 doesn't see the update available yet.
Only problem I've been having is that it crashes my graphics drivers periodically (Nvidia 189.5 I think). But performance is great and once I got my normal status bar back, I really like Firefox 4. Big fan of Sync too and looking forward to having Firefox 4 available in the Ubuntu repositories.
URL Bar (Score:5, Insightful)
as well as URL bar enhancements
If by "enhancements" they mean "throw the awesomebar out a window", I'm all for it.
Yes, part of that is resistance to change, but part is from my first experience involved typing a URL and seeing results getting pulled from the middle of a page's title that had nothing to do with what I wanted.
and it's slow (Score:3)
That and it's terribly slow. When I want to check websites, I check five. I type one press enter, then CTRL+T, and then start typing. But by tab 3, Firefox is too busy rendering to bother returning the URL results in any timely fashion. I can usually finish typing the url before it's found a result for me.
I credit this to the thugs in charge with superiority complexes who refuse to admit something is wrong and needs fixing.
Opera&Chrome are supremely smoother. One of these days I will just jump ship to O
Re: (Score:2)
Re: (Score:3)
Uh ... no. You are not recalling correctly. The Awful Bar cannot be turned off. There is an extension which attempts to restore the URL bar to its previous functionality but it doesn't work.
Let's review. I used to be able to click on the URL bar and drop down a list of all the URLs I ha
Re: (Score:2)
Only if you had visited it by typing the URL. If you'd got there by following a link, it wouldn't be there. Given the likelihood of one of those vs the other, I personally found the drop down "typed URL history" completely useless. The history, on the other hand, contains all the visited sites - whether typed or not - so you can still look there to find it.
Better yet, if you remember
Re: (Score:2)
Yes, that is what I was referring to. I may not have said it clearly.
Re: (Score:2)
Re: (Score:2)
The URL bar now drops down a list of random URLs that has absolutely no relation to anything I have recently entered manually. What a load of crap.
That would be the History feature, View... By Last Visited. Or by date & site, if you prefer.
Re: (Score:2)
Forgot the video id of that youtube video you want to show to a friend? Didn't bookmark or subscribe to that thread on a forum? Just type a few words in the Awesome Bar and you'll usually have it right there in the top ten results.
Re: (Score:2)
No they're not. I just dropped down the list and one of the the items is from about a week ago and all the rest are much older. It isn't showing recent browsing history, it isn't showing URLs I've recently typed in manually. It isn't showing anything even remotely useful.
Re: (Score:2)
It's a bug that the FF developers don't believe exists. Please see https://bugzilla.mozilla.org/show_bug.cgi?id=620723.
Re:URL Bar (Score:5, Insightful)
As a long time Firefox user, this has been one of the most infuriating things, as they continually remove or fuck up useful features. The Mozilla developers seem obsessed with changing things just to make them different. The list of things they have eliminated or made less useful is almost endless. I'm sure they can give us all sorts of rationalizations for what they do, but it's all bullshit. Making things less useful is not an improvement.
Re: (Score:2)
What sort of things? And was Awesomebar really that infuriating? Are people paralyzed by seeing the dropdown options as they type? Seems sooooo much easier than using the history panel to me.
Re: (Score:3)
Yes, awesomebar IS that infuriating. Paralyzed by seeing options, no, but give us the option to turn off behavior we don't like. Is it THAT hard to do?
No. It isn't. It is simply the devs saying "this is a better way, and you'll use it whether you like it or not", which isn't a cool attitude if you want to keep your user base.
And yes, I've switched away from FF for that reason -- not that awesomebar chased me away, but the attitudes of the devs did.
Re:URL Bar (Score:5, Informative)
Yes, awesomebar IS that infuriating. Paralyzed by seeing options, no, but give us the option to turn off behavior we don't like. Is it THAT hard to do?
No, you only need to hit "edit"->"Preferences"->"Privacy" and in the "Location bar" section, where it says "when using the location bar, suggest:" just select "Nothing" from the dropdown menu.
Now that you know that, if it is that infuriating then how come you failed to even look at Firefox's preferences to disable it?
On the side note, I love the awesome bar. I configured it to display only bookmarked links (that option is also available in the dropdown menu I mentioned) and now, instead of clicking through multiple menus or, *ghasp*, use a search engine, I just hit Ctrl+L, type a couple of keys and voila: I'm opening the link. You say infuriating? I say godsend.
Re:URL Bar (Score:5, Informative)
As a long time Firefox user, this has been one of the most infuriating things, as they continually remove or fuck up useful features. The Mozilla developers seem obsessed with changing things just to make them different. The list of things they have eliminated or made less useful is almost endless. I'm sure they can give us all sorts of rationalizations for what they do, but it's all bullshit. Making things less useful is not an improvement.
I'm a Firefox developer. I understand that it can seem that way, but trust me, a lot of thought goes into each change we make. I'm not saying we are always right, or even always right for most people - nobody's perfect. But I do think that overall we do a good job, in picking what to change, and for the specific stuff you dislike, most of it should be configurable through prefs.
But, I realize that doesn't help you, and I'm sorry that some of our changes are not to your taste.
Re: (Score:2)
It's not a matter of "taste". Tabs on top versus tabs on bottom is a matter of taste. The orange Firefox button versus a regular menu bar is a matter of taste. Removing functionality, so that I can no longer do things that I used to be able to do is not a matter of "taste"..
Re: (Score:3)
Re: (Score:3)
Thanks, but the "add-on bar" just shows add-on options, it does not provide the most important function of the status bar - looking up URL on mouseover.
This drive to kill URLs and replace them with keywords, which mozilla has been doing since 3.0 and the "smart-ass" address bar just went over the top.
I know that the starting few characters of URLS are now shown in the address bar, however the address bar isn't even close to long enough to display two URLs properly.
And I run on >1500 horizontal resolution
Re: (Score:3)
The big issue, though, it FF dev's attitude of 'F-U, learn to like it.'
Not sure where you got that impression - I'm a Firefox dev, and I definitely don't think that way. As I said above, I'm sad when people don't like our changes.
I love the awesome bar (Score:2)
I seriously hope Firefox doesn't change how the awesome bar works. That's one of the many things I prefer in Firefox to Chrome and all other browsers.
Re: (Score:2)
Yes. I love the awesome bar as well. I just wish there was some way to let the general public know how awesome the awesome bar was.
Now I'm not in marketing, but maybe if we started calling it the Really Really Good bar?
Re: (Score:2)
Me too. The combination of the aweseome bar with the Ctrl+L shortcut key let's me use my browser without having to rummage through countless menus and sub-menus of bookmarks and the like.
Adding to that, I simply don't understand those "OMG awesoembar is teh suck!!1!" people, not because they don't like it (or even gave it a try) but because they can simply turn the god-damned feature off in the options menu. It isn't even necessary to go through the about:config. Just click on the dropdown menu and prest
Re: (Score:2)
If by "enhancements" they mean "throw the awesomebar out a window", I'm all for it.
I'm actually quite a fan of the awesome bar. I know i'm probably in the minority around here, but when I create a bookmark I just add a few tags to the bookmark and I'm done. No more having to go through folders and submenus of bookmarks. Also makes it easier to search through my history, especially if I want to run the same google query. Makes it pretty handy in that respect.
I know that if you have a bad experience you tell 10 people and if you have a good experience you tell 1 person.
Re:URL Bar (Score:5, Insightful)
Re: (Score:3)
I had to go back to Firefox because I found the Omnibox utterly useless for how I use an address bar. After getting used to the Awesomebar I have no idea how anyone could use the Chrome one and think it was better.
If Omnibox gave higher priority to keywords in my history like Awesomebar does it would be great, but at the moment if you're used to Awesomebar its almost impossible to adapt.
fine-tuned add-ons manager (Score:3)
Can this thing prevent covert, un-removable install of add-ons (e.g. .NET Framework Assistant)?
Does it set layout.css.visited_links_enabled to false?
(See http://yro.slashdot.org/comments.pl?sid=1894680&cid=34430992 [slashdot.org])
Re: (Score:3)
Re: (Score:2)
I just wish there was an easier way to track down and uninstall/delete the particular addon/plugin. about:plugins is only slightly helpful – it doesn’t even tell you where the .dll files are located (the plugins.dat file does, but you can’t edit it – it’s automatically generated).
And I have no idea how it even figures out where all of its plugins are located, either... apparently the [HKCU|HKLM]\Software\MozillaPlugins registry keys have something to do with it, as does the %pr
Re: (Score:3)
In other words, it's Mozilla's fault that this is possible, and we're still waiting for a Firefox release that fixes the bug.
How do you plan to allow Mozilla to install per-user addons without allowing other programs to install addons when logged in as the same user?
If Mozilla runs addons in ~/.addons, then anyone can put one there. If Mozilla reads a list of addons from ~/.addons.list, then any program can add one to it. You can only prevent programs from adding addons by preventing users from changing that configuration, which then means they have to be root or some other privileged user in order to install the addons that they
Re: (Score:2)
Yeah... or implement some sort of signing for a list of allowed extensions.
And how do you plan to do that?
If Mozilla can sign an arbitrary list of extensions automatically, then any other application can, even if it has to go poking around inside the Mozilla executable to extract the signing key.
Re: (Score:2)
Why do you need to tell me you're completely pathetic?
Re: (Score:2)
That's exactly right. Just like it's GM's fault that the cup of coffee I put in a cupholder in my car spilled on my pants when I stomped on the gas pedal (To use one of the oh-so-popular car analogies that I understand is mandatory on this site).
Is it Mozilla's fault that you can install an add-on? No. Is it Microsoft's fault that they didn't ask before installing the add-on in question? Yes! Is it Mozilla's fault that the add-on is not uninstallable from within Firefox? No (MS put the add-on in question in
Is "Beta" an appropriate label? (Score:3)
It seems to me that if they cleared 1400+ bugs between Beta 7 and Beta 8, then there's a whole lot of significant bugs that still need to be fixed. That doesn't sound like what I'd call "Beta".
Re:Is "Beta" an appropriate label? (Score:4, Insightful)
Re: (Score:2)
I thought alpha meant the feature set and API are not stable, beta meant the feature set and API are stable but there are release-critical bugs, and final meant that there are no more release-critical bugs?
Re: (Score:2)
You'd think, but the sibling comment says they were adding features until Beta 7. Might as well just call it the Flarmflooz 7 release if words don't have meanings.
Reading a bunch of comments here leads me to believe Beta 9 will be where most beta testers should expect to jump on board.
Good but great? (Score:2)
Re: (Score:2)
I like that firefox wants to be fast and everything but does it even matter anymore. I have at least 10-15 extensions in my browser and at least one of them keep crashing/leaking memory etc. Does this release have a better plugin container for these extensions?
Firefox 4 will ship with much better plugin and extension support. Plugins already run in a separate process in 3.6, while in FF4 you can also write addons that run that way (using Jetpack). Note that addons will need to have changes made to them, so this won't immediately fix all of these issues if you use older plugins. But, it's a major step forward, and most major plugins are already in the process of updating to FF4.
"It hurts when I do this, doctor..." (Score:2)
Figure out what the plugin is and stop using it. Fixed.
This is why a lot of app developers hate plugins, etc. because their product gets blamed for some cute "dancing reindeer" add-on that leaks memory and now their product "totally sucks!"
If you think Chrome will solve your problem, you will be sad. The sandboxing is to prevent a plug crash from taking down the whole browser, but it's perfectly fine for it to consume memory. And Chrome, particularly the latest dev build, is a resource monster already. As m
Re: (Score:2)
No it's not (Score:3)
The download links are still pointing to beta 7.
https://www.mozilla.com/en-US/firefox/all-beta.html
addons (Score:2)
The main reason I run FF is the wealth of addons.
Will 4.0 break compatibility?
Yeah. Delicious toolbar specifically (Score:2)
Can't migrate til that is compatible.
(Yeah I heard the news.)
Re: (Score:2)
Does the Pope shit in the woods?
But seriously. The answer is YES! Almost none of your extensions from FF 3.6 will work with FF4. If you are lucky, there might new new versions available. But that is not always the case. It is very common for people to create extensions, sometimes really nice useful ones, and then abandon them.
Re: (Score:2)
I don't know. Are there many woods in Vatican City?
The question was about the extent of the breaking changes. Quite a number of addons that I use are "abandoned" and technically inco
Re: (Score:2)
It is very common for people to create extensions, sometimes really nice useful ones, and then abandon them.
It’s usually not difficult at all to make them work, though it’s (by design) hidden well enough that you have to look for it.
While Firefox is not running:
%userprofile%\Application Data\Mozilla\Firefox\Profiles\*\extensions\
Browse into each extension’s folder one-by-one, open install.rdf in a text editor and read the <em:name> definition near the top until you find the correct extension. Once you find it, just scroll down to the <em:maxVersion> definition, and change to suit. Sa
Will it support languages other than JavaScript? (Score:3)
Will it finally support languages other than JavaScript for client side programming? Just when we seem to be entering a point in time where people finally realize that they can choose the right language for the job, so much is moving to the web where there's only one language or nothing at all.
Re: (Score:2)
Re:Will it support languages other than JavaScript (Score:4, Interesting)
> Will it finally support languages other than JavaScript for client side programming?
No.
In fact, we're _removing_ such support. We supported using python for chrome (Firefox browser ui, not google's browser) programming for years, and no one used it. It's just a performance drag on the javascript and C++ side of things, so it's being removed.
The fact is, supporting multiple languages in a single runtime without leaking and without nasty performance hits on both is not really all that feasible. Given that, and the near-zero amount of actual use such functionality would get, based on our experience with chrome, it's not worth building it in....
Re: (Score:2)
A neat demo, to be sure, but it's not compiling. It's just interpreting Python into JavaScript which is itself interpreted. I would much rather see the ability to write in the language of my choice and have that compiled into bytecode which I would then serve to clients. That bytecode would be what is executed. Then we can use whatever language is best for the job.
Re: (Score:2)
Then stop using HTML/CSS/JavaScript for applications and use Java Web Start. Write in Java, Ruby (JRuby), Python (JPython), Scala, or JavaScript (Rhino).
Re: (Score:2)
But then it wouldn't be web pages.
Try it. (Score:2)
It's just as fast as Chromium now, and with many windows and tabs and after being open for days it seems less of a resource hog than Chromium. Only the startup takes longer, at least with several extensions. There's a Greasemonkey beta for it too now - the last reason that held me back from setting FF as my default browser again.
Want to help? Test Hardware Acceleration... (Score:2)
If you do get the beta, go and run this add-on, https://addons.mozilla.org/en-US/firefox/addon/200733/ [mozilla.org]
It will help the Firefox developers learn how best to use hardware acceleration.
1415 bugs fixed... (Score:2, Insightful)
Re: (Score:3)
Firefox uses the Windows system (since you’re obviously on Windows) to render fonts. I suggest you change your font settings under Display Properties, Appearance, Effects. I like ClearType. YMMV. If you turn on ClearType you might also want to tweak the settings with the ClearType tuner [google.com].
And IIRC it’s completely different in Win7, and I can only test it on Windows XP right now, so it’s up to you and Google in that case.
JS Benchmarks (Score:3)
Are we fast yet.com [arewefastyet.com] shows the measurements used by the Mozilla Javascript development team, comparing performance of ff4 to chrome/v8 and safari/nitro using both the sunspider (Mozilla) and v8bench (Google) test suites. LOTS of movement in Firefox over the past few months, including the apparent surpassing of Safari's Nitro engine in both tests and even beating Chrome's V8 in the Mozilla test suite.
This boost is likely due in part to the recently added hardware acceleration [mozilla.org]. This is listed as supported on all major operating systems (see the Firefox 4 Beta Technology [mozilla.com] page).
Re: (Score:3)
How is it possible? Easy. Last month there was an entry in Bugzilla where they fixed a bug that was submitted in November 2000. That's right 10 years ago -- before Firefox even existed. It means that Firefox is still running old Mozilla code from a decade ago.
Re: (Score:2)
I'm not sure if he was defending Mozilla so much as pointing out that Firefox is not exactly running on all-new code, which takes them 10 years to fix on occasion.
Re: (Score:2)
Exactly. When some of your code is 10+ years old, it's not surprising that you can find lots of bugs.
Re: (Score:3)
Re: (Score:3)
> it's really REALLY hard to utilize any of regular expression stream tokenizers
Uh... you can't tokenize HTML (correctly at least) with regular expressions. If you're trying to, you just lose. If you're doing it for security reasons, you _really_ lose.
> so "dozens" turns to "few" under scrutiny..
Uh... "dozens" and "a few dozen" are in fact pretty much the same last I checked. "few" and "a few dozen" are not. Please do read what I wrote instead of just trolling?
> i'm sure there was at least 1 bu
Re: (Score:2)
i seriously need them to release ff4. enough beta-ing around already!!1
Re: (Score:2, Insightful)
i seriously need them to release ff4. enough beta-ing around already!!1
So you would rather have buggy code as long as that it is released? use IE!
Roll a d20, save VS Stupidity......
Re: (Score:2)
I think I'll wait intil it's less buggy. This one has 1415 bug fixes, how many more bugs are there?
Re: (Score:2)
Firefox 4 goes up to 11!
Re: (Score:3)
Re: (Score:2)
That's odd. I downloaded beta 8 within minutes after this story was posted.