Archive for the ‘FireFox’ Category

Another reason to call FF 3.5 an epic FAIL

Wednesday, October 7th, 2009

So, there’s been some complaining on the Web about FF 3.5. With 3.0, the FireFox team pulled out a great browser that was faster, standards compliant (close enough) and a better alternative to IE 7′s aging alternative.

But 3.5 seemed like a rushed release. I mean, 3.0 was chugging along just fine (for me at least) and suddenly we went from 3.0.x to 3.5? It’s not like there was anything (beyond an engine upgrade) worthy of  a that big a release. Make it a 3.1 or something.

I digress. So, what’s the reason to hate 3.5? JavaScript execution. Seems there’s an issue that makes life harder for Web developers. If you’ve got a JS include in your Web page and there’s an interpreter issue (e.g. typo in a function name) or an Ajax timing issue (e.g. Ajax call hits earlier than expected), instead of outputting an error some where (even in FireBug) isn’t happening.

I was porting some code over from a page into an include JS file and discovered this wonder as JS execution just stopped at some point. Eventually I managed to track it down to some functions that were missing from the page (weren’t copy over). No thanks to FireBug or the Error Console. IE? Oh, IE’s fun…it just keeps running the JS without generating an error…but that’s IE.

Still trying to figure out a different issue related to Ajax calls bumping into each other (at least that’s my guess) but found something interesting. JSLint is a “JavaScript Code Quality Tool”. Not the best tool (it doesn’t know what the “navigator” object is and I got an error because “alert is not defined”…it’s part of the friggin standard!) but it definitely helps zero in a bit on possible issues–better than a line by line walk through miles of code.

Mozilla: please, please put together a 4.0 release that basically goes back to the 3.0 release…but is faster and better of course. You’re fucking up your lead big time.

out

FireFox: Where hath my memory gone?

Friday, July 24th, 2009
Time to cut down?

Time to cut down?

Wow, Firefox is zero for two this month…even if it is by association. I’m a Web developer (shut up about the site, douche) and not so long ago switched over from the drudgery of IE7 to FF3 as my standard, regular, wake up in the morning next to her browser.

IE7 decided to have a stroke and die on my machine (despite a recent rebuild of the machine) that seems to resemble dimentia. It started with 1 out of 10 times I’d load the browser it would sit there stuck trying to connect to a site and no matter what you did (stopped, clicked a bookmark, whatever), it had no idea how to do its job. Over time that escalated until it was 8 out of 10 times.  Meanwhile, Firefox, you mynx, delivered Web site after Web site like a slave girl delivering grapes.

So, I made the switch and never looked back. Until, I started noticing how things would slow down towards the end of the day. Nothing too major but if you left and came back 15 minutes later it would take a little while for things to get humming along. At first, I thought, maybe it’s that Western Digital “Green” drive I got, not realizing “green” means “slower”. But then I checked the processes running. Now, I’m running SQL Server (Developer Edition) and Visual Studio 2005, both memory hogs but surprisingly they were up there but not the worst offender. No, the worst offender at 500 MB of my precious 2GB of RAM was Fire-fucking-Fox.

Where's the Downsize button?

Where's the Downsize button?

Hurgh? What in blazes does a fucking browser need 500 MB to run? I run some add-ons like Firebug and Web Developer Toolbar. So I did the diagnostic thing and turned everything off and then brought them back in one at a time.

Step one: Everything. 160MB -> 46MB. So, we have a culprit. Then waste a lot of time doing this:

Firefox Bare 46.5 Delta
AVG 53.1 6.6
Aviary 53.5 0.4
Battlefield Heroes Updater 54.6 1.1
Firebug 67.5 12.9
Firecookie 68.1 0.6
FoxyTunes 74.3 6.2
Microsoft .Net Framework Assistant 1.1 75.1 0.8
Pixel Perfect 75.2 0.1
Real Player Recorder 77.6 2.4
Web Developer Toolbar 77.8 0.2
Open a blank tab 78.3 0.5
Go to FogBugz (server-side site) 83.4 5.1
Open third tab 92.8 9.4
Go to Amazon.com 114.7 21.9
Close third tab (Amazon) 110.6 (4.1)
Close second tab (FogBugz) 103.4 (7.2)
Close final tab (switches to blank tab) 103.7 0.3
Open a new window, blank 104.7 1.0
Deactivate all add-ons (launch blank) 33.6 (71.1)
Load this site’s admin 44.0 10.4

What does it all mean? Add-Ons + Multiple tabs and windows + a few hours = memory hog. And, it seems I’m not the only one complaining about this…there are even how-to‘s dedicated to memory and Firefox! (I like the offline cache…512MB??)  But, c’mon, the average user isn’t going to even know there’s a problem…except to know that when they run Firefox, things seem to slow down.

Now, while I’m putting a lot of the blame on the add-on creators, it’s not all them. Look at how much memory is required to open ONE friggin extra tab. 9MB? So much for Open Source…maybe the problem isn’t that a bunch of disparate virtualized coders are about as easy to organize as a herd of cats.

Maybe it’s the same problem that Microsoft has…you know that big company where you could not meet 90% of the company even if you spent 10 years there. Maybe the problem is, we’re too used to the idea that with plentiful memory, the maxim that dictates that an organism, given an environment of a specific size, will grow to fit that environment. And don’t get me started with Chrome…

Maybe it’s time we sell PCs with 256MB of RAM and force developers to remember how to keep things tidy and need. Maybe–oh, wait, there’s a new version of FireFox out! I should get some more RAM and download that sucker!

out

Firefox Bare 46.5 Delta
AVG 53.1 6.6
Aviary 53.5 0.4
Battlefield Heroes Updater 54.6 1.1
Firebug 67.5 12.9
Firecookie 68.1 0.6
FoxyTunes 74.3 6.2
Microsoft .Net Framework Assistant 1.1 75.1 0.8
Pixel Perfect 75.2 0.1
Real Player Recorder 77.6 2.4
Web Developer Toolbar 77.8 0.2
Open a blank tab 78.3 0.5
Go to FogBugz (server-side site) 83.4 5.1
Open third tab 92.8 9.4
Go to Amazon.com 114.7 21.9
Close third tab (Amazon) 110.6 (4.1)
Close second tab (FogBugz) 103.4 (7.2)
Close final tab (switches to blank tab) 103.7 0.3
Open a new window, blank 104.7 1.0
Deactivate all add-ons (launch blank) 33.6 (71.1)
Load this site’s admin 44.0 10.4

FireFox: Hates Macs and your cookies…

Monday, July 13th, 2009

As much as I’ve been finding myself dragged over to the FF camp over the last year, there have been some dark clouds over the browser that would be king.

First, it seems either no one is testing FF3 on the Mac or whoever it is that’s testing it doesn’t realize that not everyone can use a mouse when using a browser. I can but others can’t and when you make it so that drop-downs and checkboxes and radio buttons are not selectable via keyboard….only by mouse click…people with disabilities who might be using a key that–wow, everyone, uses–are sort of left out of the loop…ouch.

It’s real simple…just fucking focus on the damned control! Why is that so hard? Just a little code…just a simple hack. Nutters.

Second, this one just fucked me today actually. Turns out, when you’re about to REMOVE ALL YOUR COOKIES because you’re half-asleep and thought the Remove ALL Cookies button looked a hell of a lot like the Remove Cookie (singluar bitches) right next to it, no one at Mozilla thought it might be worth putting in a confirmation alert to be sure you want to fucking WIPE all your cookies. FFS, I don’t remember all my fucking logins and now I’ve got to figure them all out again. Thanks, Mozilla. Your laziness over a few lines of code just added to the time I have to spend remembering (or using those forgot pass links).

I never understand why it’s so hard when you’ve got a full team of developers (one man shows are harsher) and QA people to build solid products, regardless of platform.

So much for that Web platform…next?