8 ms·
Good news: Mozilla fixed their damn browser
- redmethod 15y agoEven with fixes, most people seem to be switching to Chrome. It's hard to beat Google's integration
- wwweston 15y agoGoogle's integration is actually the reason why I'd switch back to Firefox in a heartbeat if the performance kept up -- there's some serious privacy issues involved in browsing the web using a Google browser while logged in to a Google account.
- happyfeet 15y agoAbsolutely. Most often I catch myself do private browsing in Chrome and 'feel' safer with Firefox. May be my fears are unfounded and yet I do it often.
- pyre 15y agoI like Chrome's "private browsing" mode better than Firefox's though. Mostly because I can have private and non-private windows open at the same time (and they're properly sandboxed from each other).
- gruturo 15y ago./firefox -P someotherprofile -no-remote (assuming you created someotherprofile via Profile Manager - it's dead easy) (Works on Windows, too)
- pyre 15y agoRight, but in Chrome it's as easy as Ctrl + Shift + n from another Chrome window. edit: I'll note that I don't believe that the parent to this post should be down-voted. It was informative and on-topic.
- gruturo 15y agoMaybe I would have deserved a downvote for forgetting to mention that after opening the second Firefox session you still have to switch it to Private Browsing :-))))
- redmethod 15y agoTrue. I'm not saying that google's integration is necessarily a good thing, but many people like having everything easily accessible, and don't consider the downsides to putting all their private eggs in one basket. I keep wanting Opera to be faster and better on Mac OS X, and while I enjoy Firefox, I'm not a huge fan of the design of it on a Mac.
- NARKOZ 15y agoUse Chromium if you complain about privacy
- gcp 15y agoI don't see how Chromium solves any of the issues he was complaining about. It's not like it rips out the basic designs of the browser, which are still tightly tied to Google.
- intranation 15y agoChromium and Chrome are identical except for one compile flag (which means you can at least check it yourself): http://news.ycombinator.com/item?id=3034755 http://news.ycombinator.com/item?id=3034755
- kakuri 15y agoSRWare distributes a Chromium build called Iron that strips out privacy problems. http://www.srware.net/en/software_srware_iron.php http://www.srware.net/en/software_srware_iron.php
- otherpope 15y agoI used to recommend Iron but I don't anymore. I became increasingly uncomfortable with the lack of documentation and lack of transparency in the project. They delivered their source code as two code dumps on rapidshare last time I checked. Something just doesn't feel right at all.
- bad_user 15y agoWhat integration are you talking about?
- rhizome 15y agoIt would be more accurate to say "is (probably) fixing," possibly with an (on Linux) suffix.
- sciurus 15y agoCan anyone point to the bugzilla entries for the fixes?
- mbrubeck 15y agoI'm not sure which exact bug was the culprit here, but this is a list of related to responsiveness problems caused by the "places" database: https://bugzilla.mozilla.org/showdependencytree.cgi?id=691507 https://bugzilla.mozilla.org/showdependencytree.cgi?id=69150... Some notable ones that were fixed recently include http://bugzil.la/690354 http://bugzil.la/690354 and http://bugzil.la/686025 http://bugzil.la/686025
- jmillikin 15y agoNot to discount the work that Mozilla has been doing, but it seems like the "improvement" they added is actually just a workaround for distros that configure filesystems incorrectly. That is, his machine is configured to use an obsolete filesystem (ext3) in a mode with significant performance problems (data=ordered). There are numerous ways that a machine can be mis-configured such that it suffers from poor performance. It would be better if Firefox detected these and warned about them, rather than just silently working around the broken-ness.
- talmand 15y agoBut this is a common theme with people who label software as bad. It's possible the problem is something other than the software being used, but since they only see the problem while using said software then obviously the problem is the software itself.
- CrLf 15y agoI find these statements amusing... As it happens, neither is ext3 an obsolete filesystem (I have many machines using it just fine, thank you, with no intention to migrate to less tested filesystems just because they're "new"), nor "data=ordered" has significant performance problems. More amusing than this just the fact that the filesystem is a bottleneck for a web browser... an application that should be network and CPU bound...
- nohat 15y agoI would agree that calling ext3 obsolete is odd, but I don't know enough about the particulars of file system performance to understand why data=ordered is or is not problematic. This leads to the interesting problem of judging the opinion of several contradicting, but apparently similarly qualified people. I'm sure someone on HN is able to decisively explain: can someone do so?
- yew 15y agoOriginally, ext3 filesystems maintained journals of all metadata and data changes. This substantially decreases the likelihood of the filesystem ending up in an irrecoverably inconsistent state, but it also has major performance implications. Relatively early on ext3 was extended with "data=ordered" and "data=writeback" modes (with "data=ordered" being the default and recommended mode, as "data=writeback" is marginally faster but offers few consistency guarantees). In these modes only metadata changes are committed to the journal. In "data=ordered" mode the filesystem attempts to guarantee that data will actually be written to the disk (not merely cached) before any related metadata writes occur, as opposed to caching and writing all data according to an outside schedule. Obviously, this also has certain implications for write performance. I would say that Firefox was incontrovertibly broken in this case, but my views on the adoption of ext4 would probably be considered rather conservative. Regardless, ext3 isn't going away any time soon so this fix will be appreciated.
- joejohnson 15y agoWhat are people's overall impressions of Firefox 9?
- viraptor 15y agoI don't remember anymore - running 11.0a now. I'm using nightly builds since ~2009 and haven't experienced any issues so far (really - not even a random crash). The difference is so huge in overall performance, I don't want to go to the "stable" release anymore. The only problem are some less common plugins, but adblock and firebug get updated within days... and I just switch to the latest official release for quake live.
- otherpope 15y ago"I don't remember anymore - running 11.0a now. I'm using nightly builds since ~2009" Likewise. I also have several extensions enabled and generally have 30+ tabs open all the time, sometimes many times that. I have had an odd crash but very rarely.
- noelwelsh 15y agoI've been running Aurora for a few months. It's been stable and gets the new toys quicker. Some add-ons break on some updates, but the few web dev. add-ons I use are always quick to update. I get questionnaires from time to time, but they don't take long to complete and are a trivial way to contribute to Mozilla. In short, give Aurora a try. It works as my full-time browser.
- zobzu 15y agoNote that you can disable the questionnaires if you don't like them (you do, but some may not)
- cpeterso 15y agoI've been running Aurora for six months without any major problems. The only annoyance was some Add-ons were disabled, but Mozilla's Add-on Compatibility Reporter Add-on allows you to force-enable older Add-ons. That said, I think this Aurora release cycle will automatically opt-in all Add-ons.
- deleted 15y ago[deleted]
- PissedOffHNer 15y agoFixed? I ran Google Chrome open with 80-100 tabs for 3 WEEKS without anything going wrong. Sunday the 18th I finally closed it and restarted my computer (after 3 weeks of non stop running). Monday I launched the latest build of FireFox and within 30 minutes it crashed. It then crashed again a few hours later. Goodbye FireFox.
- Athtar 15y agoThis is unfortunately my main issue with FF. I am type of person that has multiple tabs open in multiple windows for days at a time and FF tends to choke in that scenario after a few days. I was hoping the 64-bit version might fix the issue but it's even worse. It's still my main browser but this one issue just kills the entire experience.
- zobzu 15y agoI ran Chrome for 4 years (yeah) and closed it today after this news. Started Firefox Aurora and it crashed at opening. Damn. Oh and this is my 3rd post.
- cpeterso 15y agoTo be fair, Aurora is Mozilla's not-even-beta channel. And today of all days was Day 1 of a new Aurora release cycle: in 6 weeks - 1 day, Aurora will be elevated to Beta channel.
- PissedOffHNer 15y agoI saw the downvotes and just chuckled. I literally DID have it open for 3 weeks. What I posted DID happen, no exaggerations.
- jrockway 15y agoI would blame Flash for this.
- tytso 15y agoSo a couple of corrections that people are getting wrong over and over again in this discussion. The reason why data=ordered is the default is not because it's more likely for the file system to be recovered after a crash. It's default for security reasons. The "data-writeback" mount option has the tradeoff that there can be uninitialized blocks attached to files after a crash. These uninitialized blocks could contain someone else's love letters, porn stash, medical records, etc. The main issue with "data=ordered" is not that it imposes a global order, but that if you do block allocations, fsync() requires a journal commit, and the security guarantees behind "data=ordered" require that all newly allocated blocks must be written out before the filesystem-wide journal commit can be allowed to complete. (Ext4 doesn't have this problem because it uses delayed allocation.) This isn't an issue with other databases such as Oracle, DB2, MySQL, etc. They have no problems running on ext3. This is partially because they don't use fsync() at all. Oracle and DB2 use O_DIRECT to blocks that are allocated once (new blocks are only allocated when the table space file needs to be grown), and MySQL uses fdatasync() to files that aren't constantly being created and destroyed. SqlLite, because it is trying to pretend that it only needs one file, uses many, MANY temporary files which are being constantly created and destroyed. This is not efficient, and is why SQLite has all of these problems, but millions and millions of dollars worth of enterprise servers can use ext3 running on RHEL3, RHEL4, and RHEL5 on Oracle without hitting these issues. The sad thing is most people like to use SQLite because it doesn't require manual scheme generation, not because it only uses one file. (In fact it doesn't; there are multiple temporary files, some of such must be there in case of an unclean shutdown. So if you copy just the single file after a program crash, you'll screw up the database.) If someone created a lightweight database that uses SQLite's interfaces, but used a single directory to hold all of the database's files, and then didn't constantly copy data back and forth between temporary files which were being constantly created and destroyed, but instead used the storage strategies used by the more sophisticated database systems, the result would work well on ext3, and for all file systems, it would use less data writes, which would save battery usage, SSD write endurance, and many other things. The last time I measured it, Firefox's "awesome bar" was consuming a third of a megabyte of write bandwidth to the disk per click; and it was updating at most a few hundred bytes of data. The rest was all overhead due to the catastrophic inefficiencies of SQLite. P.S. And if you do implement this, please consider releasing it under the Apache license so I can hopefully convince the Android team to drop SQLite in favor of something that was a bit more written towards performance --- and Android users all over the world will thank you. :-)