Comments on: Was Firefox 2 a mistake? http://www.p2pnet.net/story/10260 p2pnet.net - reader powered Mon, 23 Nov 2009 05:30:38 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: Reader's Write http://www.p2pnet.net/story/10260/comment-page-1#comment-129552 Reader's Write Tue, 31 Oct 2006 06:18:22 +0000 #comment-129552 I experienced the freezing issue (which is memory leak) numerous times. When this caused actual loss of information, I restarted the computer for like the 5th time since getting FF2 and then downgraded to 1.5.7. The other issues I have with 2.0 is the Mac-style themes do not work with it (aesthetic issue, considering the rest of my XP looks just like a Mac mostly). I'm impressed with IE7 overall, but that still has a long way to go. I'm glad they improved the tab interface since beta 1. Neat is that IE Tab for Firefox loads IE6, just in case I need it for web development. I hope a fix will be coming out soon, I was expecting it within days, rather than developers and users acting as if they don't exist just because they don't receive those problems. When the fix is official and is confirmed by others as working without the memory leaking issue, I will then upgrade again. By then, my favorite Mac theme will hopefully be done for 2.0. I experienced the freezing issue (which is memory leak) numerous times. When this caused actual loss of information, I restarted the computer for like the 5th time since getting FF2 and then downgraded to 1.5.7. The other issues I have with 2.0 is the Mac-style themes do not work with it (aesthetic issue, considering the rest of my XP looks just like a Mac mostly).

I’m impressed with IE7 overall, but that still has a long way to go. I’m glad they improved the tab interface since beta 1. Neat is that IE Tab for Firefox loads IE6, just in case I need it for web development.

I hope a fix will be coming out soon, I was expecting it within days, rather than developers and users acting as if they don’t exist just because they don’t receive those problems. When the fix is official and is confirmed by others as working without the memory leaking issue, I will then upgrade again. By then, my favorite Mac theme will hopefully be done for 2.0.

]]> By: Reader's Write http://www.p2pnet.net/story/10260/comment-page-1#comment-129547 Reader's Write Mon, 30 Oct 2006 21:49:07 +0000 #comment-129547 Admittedly, I've been an on-the-fence browser user for the past couple of years -- being unable to decide between Firefox, MSIE and Maxthon browser. Firefox 2.0 does have its problems, as mentioned in this article -- but it will inevitably come with an array of updates and bug-fixes. Never the less, I think I've made my decision to stick with Firefox for the time being -- FF2.0 has a lot of the features which had previously thrown me off using earlier versions. It's an evolving application -- and no, I don't think we're taking two steps backwards with FF2.0 - Bauer Admittedly, I’ve been an on-the-fence browser user for the past couple of years — being unable to decide between Firefox, MSIE and Maxthon browser.

Firefox 2.0 does have its problems, as mentioned in this article — but it will inevitably come with an array of updates and bug-fixes.

Never the less, I think I’ve made my decision to stick with Firefox for the time being — FF2.0 has a lot of the features which had previously thrown me off using earlier versions.

It’s an evolving application — and no, I don’t think we’re taking two steps backwards with FF2.0

- Bauer

]]> By: Reader's Write http://www.p2pnet.net/story/10260/comment-page-1#comment-129542 Reader's Write Mon, 30 Oct 2006 19:17:54 +0000 #comment-129542 FWIW, I was experiencing severe resource hogging in 1.5.x which now seems to have gone away, and (luckily) haven't seen the freezing issue, although I have been testing since the first RC became available. Obvioulsy this affects some people and is serious, but I have no doubt a fix for this will be released soon. As for extension incompatibilities, this was a minor irritant a few weeks ago but most of the twenty or so extensions I use had been updated by the official relase, and all are now up to date. FF2.0 has a nifty new feature where incompatible extensions are disabled, but the browser searches for and downloads compatible versions when it starts up, thus saving both the need to manually search for them and a restart afterwards. Meanwhile, IE7 was released with a couple of security of vulnerabilities and a fairly long list of known display bugs. (Although now the bug reporting mechanism has been closed...) The IE team have done well to come so far in a short time, but they haven't caught up yet. It's a shame they had to build on top of existing buggy code. For people who found the Firefox upgrade lacklustre, may I suggest the Flock browser (www.flock.com)? FWIW, I was experiencing severe resource hogging in 1.5.x which now seems to have gone away, and (luckily) haven’t seen the freezing issue, although I have been testing since the first RC became available. Obvioulsy this affects some people and is serious, but I have no doubt a fix for this will be released soon.

As for extension incompatibilities, this was a minor irritant a few weeks ago but most of the twenty or so extensions I use had been updated by the official relase, and all are now up to date. FF2.0 has a nifty new feature where incompatible extensions are disabled, but the browser searches for and downloads compatible versions when it starts up, thus saving both the need to manually search for them and a restart afterwards.

Meanwhile, IE7 was released with a couple of security of vulnerabilities and a fairly long list of known display bugs. (Although now the bug reporting mechanism has been closed…) The IE team have done well to come so far in a short time, but they haven’t caught up yet. It’s a shame they had to build on top of existing buggy code.

For people who found the Firefox upgrade lacklustre, may I suggest the Flock browser (www.flock.com)?

]]>