printstama.blogg.se

Firefox memory hog fix
Firefox memory hog fix











firefox memory hog fix

So for Firefox 3, Mozilla scrapped them both, replacing them with a new, unified system known as “ Places.” Before Firefox 3, bookmarks and history were stored in separate places your bookmark list was stored as an HTML file - an approach that went all the way back to the original Mosaic browser of the early 1990s - and history was stored in a custom database called “ Mork“, whose design was memorably described by Jamie Zawinski in 2004 as “ the single most braindamaged file format that I have ever seen in my nineteen year career.”Īs Zawinski’s testimony should make clear, working with those old tools was painful for the programmers involved, and as the browser grew in complexity the limitations they imposed became more and more acute. The culprit, I believe, is the mechanism that modern versions of Firefox use to keep track of your bookmarks and browsing history. And it’s been this way ever since Firefox 3 launched - three years ago. It’s busted so bad that it’s painful to use. So I don’t like that I have to write this post, but I calls ’em like I sees ’em.Īnd on the subject of Firefox as it exists today, the way I sees ’em is this: Mozilla, you need to fix your damn browser.įirefox, on Linux at least, is busted. That’s back when Bill Clinton was president.

firefox memory hog fix

I’ve been on the Mozilla fanboy train since before Firefox even existed - all the way back to the original Mozilla Suite’s Milestone 17 release, the first version after the Netscape exodus I used regularly, which Wikipedia tells me shipped on August 7, 2000. There’s nearly ten years of Mozilla advocacy tucked away in the JWM archives.

firefox memory hog fix

Longtime Readers of this blog will be aware that I have been a fan of Mozilla for a long time.

firefox memory hog fix

Dear Mozilla: Fix Your Damn Browser Already













Firefox memory hog fix