IE7 was finally launched by Microsoft yesterday and since than it has been hogging so much of media attention that I finally decided to give it a try today. This, in spite of the fact that I have installed and subsequently uninstalled the betas of IE7 on this machine at least 6 times. Each time I tried to use it, an error message would pop up within 5 seconds and terminate the session!
Today's installation had not proved to be futile though. I've been running IE7 for the past 10 minutes and my session is yet to terminate. That's a first!
I love the leaner, meaner and slicker interface, but I guess page renditions are better via Firefox. Or maybe I'm just so used to the open-source browser's renditions that anything that appears slightly different on IE7 is being deemed flawed.
But, really, the Blogger edit window definitely looks a lot better in Firefox. I've been running Minefield 3.0a1 (Firefox's nightly builds) for the past few months both at home and in the office without facing any glitches. The only problem lies with its very bad memory management. It gobbles memory in no time, especially if you are watching videos. Just look at its memory footprint after using it for a few hours and you'll really how RAM hungry your browser is. And I'm sick of open-sourse evangalists tauting this flaw as a feature. They're really not helping the open-source community by praising a flaw when it ought to be blamed.
Another thing, I already miss the online spell checker of Firefox as I type this post!
Today's installation had not proved to be futile though. I've been running IE7 for the past 10 minutes and my session is yet to terminate. That's a first!
I love the leaner, meaner and slicker interface, but I guess page renditions are better via Firefox. Or maybe I'm just so used to the open-source browser's renditions that anything that appears slightly different on IE7 is being deemed flawed.
But, really, the Blogger edit window definitely looks a lot better in Firefox. I've been running Minefield 3.0a1 (Firefox's nightly builds) for the past few months both at home and in the office without facing any glitches. The only problem lies with its very bad memory management. It gobbles memory in no time, especially if you are watching videos. Just look at its memory footprint after using it for a few hours and you'll really how RAM hungry your browser is. And I'm sick of open-sourse evangalists tauting this flaw as a feature. They're really not helping the open-source community by praising a flaw when it ought to be blamed.
Another thing, I already miss the online spell checker of Firefox as I type this post!
Comments