Showing posts with label firefox. Show all posts
Showing posts with label firefox. Show all posts
Wednesday, September 24, 2008
Tuesday, May 13, 2008
Firefox: Remove from Dock
Firefox 3 Beta on Mac OS 10.5 (Leopard) is so horrifically unstable, I finally had to remove it from my Dock.
It makes me sad. I loved the idea of Firefox, and I'm in debt to the developers in a round-about way as their once-upon-a-time best-of-breed browser helped me become a better web architect.
But now... now I'm seething. This is a small shop making over $70 Million a year, and their software crashes several times a day. I just can't take the risk anymore: I find I've been doing things in Firefox half-expecting it'll crash and I'll be able to recover from a page reload. But that's often not the case, and anyway isn't this supposed to be the Future? I don't need the Windows 98 flashbacks.
Guys (and Mitchell) - why the hate? I always loved you, I beta-tested your browsers since pre-1.0, I fought the good fight inside major corporations for your acceptance back when you were poor... and now this-- this rat-faced crashtopia.
On the bright side:
- Firebug's Joe Hewitt works for Facebook and is hopefully getting rich, one of the few to deserve it.
- Yahoo is hiring a Firebug developer, and this has Job Security written all over it.
- Safari is significantly outpacing Firefox in new browser development.
- Opera is back from the (comfy Euro-)grave with an interesting JS debugger.
- Firefox 2 with Firebug on Windows XP is still stable enough I can do all my WinXP sanity-checking there (except for MSIE of course, for which I need to consult the Quirksmode Oracle every ten seconds).
So now I find myself trying to readjust to Safari as my primary browser, since Firefox is so unreliable. And I like it fine, but for two things that have always bugged me, and for which I believe I have fixes.
First, I don't like that Safari doesn't tell me the URL of a link I'm about to click on. I guess Apple must have asked around and found people generally don't care. But I'm just geek enough to care, so I'm going to make it do that again.
Second, I think Apple made a horrific (and uncharacteristic) usability mistake when they decided that command-1 through command-0 (10) would open the cardinal bookmarks in the current tab, instead of doing what every other power application does and switch among the first 10 tabs.
I already fixed that in Tiger, so it's not a big deal. But I remain slightly frustrated that Apple still doesn't quite get tabbed browsing. I'll be sure to post the fixes back here; and Apple, my dear, if you disagree on the tab navigation item then bring it on, I love you but I'll kick your ass on this one.
That's all for now, I have another hour of playing with KeyNote before I can crash in my own right.
The palaver is (temporarily) finished.
Wednesday, April 16, 2008
Firefox Beta 3.05 for Mac: Crash me a River.
I've been trying out the latest Firefox 3 beta (Beta 5) on my various Macs. In many ways this is a huge improvement, but in one pretty important way it's a step backwards: I now get many, many crashes per day. So many that I'm starting to have a Windows flashback.
Today, for example, I can't work with it at all. Every second time (approximately) that I enter a search term in on Google, it crashes. Looks like I'll have to reinstall, which is a bummer.
This is all par for the course, after all I'm voluntarily testing software. What scares me, though, is a rumor I heard that Beta 5 is the release candidate. It is very far from stable enough to be the release candidate, and I'd hate to see the Firefox Corporation damage their reputation by releasing beta software as final.
Monday, December 03, 2007
Firefox 2.0.11.12.13.14... still a shit-show.
The well-heeled open-sourcerers over at the Firefox Corporation have been releasing ultra-minor updates at a furious pace lately.
Just days on the heels of 2.0.10, they shot me 2.0.11. And just minutes after that, my MacBook CPU spiked to >=100%, fans whirring, on a total of 8 open tabs, none of them exotic, in a single window.
And the icing on this particular turd-cake: I use a Flash blocker because Adobe can't clean up Macromedia's code enough for it to run properly on a Mac. Yes, I click every single little Flash animation that I actually want to see, and yes, it's a pain, but it generally saves me from force-quitting my browser.
So if Firefox blows so hard lately, why do I still use it as my primary browser?
One word: Firebug. It's still the best JavaScript developer's tool anywhere... possibly the best client-side web developer's tool, period.
The fact that a lot of the dumber webmasters of the universe still don't support Safari is a growing annoyance now that I'm one of the many people browsing via iPhone. Using Firefox as my primary browser was generally a safer bet. And yet, lately, with every expectation that 2.0.12 and 2.0.13 will be buggy as well,
But is it buggy enough to make me give up my Firebug?
It might be, at least for everyday browsing. I finally got around to AppleScripting command-number shortcuts for tab selection in Safari (a thing Apple, for some reason, doesn't get), so it's really just an acclimation question.
Besides, Firefox renders fonts in Ugly-Sans no matter what you do.
PS, why am I being so hard on the poor Firefox crew?
Because when you make 74 million bucks a year and you're the
number-one browser for even semi-clueful people around the world,
you can afford to spend on engineering and QA. And you have,
frankly, having built that lucrative business on the goodwill and
technical help of your users, an obligation to not screw it up.
Friday, July 20, 2007
Firefox goes to 11.
It's pretty well known that Firefox 2 for the Mac has some CPU and memory issues. It's also pretty well known that Adobe's Flash Player for Mac is a bloated, processor-hogging swine that wouldn't know an optimization if it were bit on the ass by one.
In case you have a Mac and were wondering why everything would slow down and your browser might even lock up if you were on a page with more than one YouTube video, that's the reason.
But today it got out of control. I loaded a background tab that probably had a bunch of Flash embedded in it, but I'll never know as the app locked up so fast I couldn't get to the tab. And then I saw why:
Firefox was using over one hundred percent of the CPU! It was fluctuating between 102% and 104%. Before any of you heavy math types get all huffy with your talk of impossibility, let me just say that my iPhone was docked at the time, and I think its processor can probably just about handle an extra 5% of my Macbook.
Subscribe to:
Posts (Atom)