What makes this frustrating for me is that, like the OP, I'm pretty sure I remember when Firefox didn't have these problems. We've had similar complaints from other clients, including a business client. Just yesterday we had a client complaint where, according to them, about half the time they would go to launch Firefox, they would get the message that it was already running but not responding. People often point to extensions, but the only extension she had installed was AB+. In her case, Firefox became unusable after a day or two. My girlfriend's newer Windows workstation had the same problem, but to a slightly lesser degree. This stalling issue has been widely reported by a huge number of people, and Firefox has been doing a lot of work on their memory management to fix it, but it doesn't seem to be helping. I didn't have very many tabs open (~10?), and after about 6 hours or so, hovering the pointer over a link would give me the rainbow pinwheel, clicking a link would give me a rainbow pinwheel, opening a tab would give me a rainbow pinwheel, etc. On my older laptop, Firefox became unusable, and got worse with each version, not better. The "hanging" issue: I literally just replaced a laptop because of this one.
It's not so much that Chrome is great, as that it doesn't seem to have the faults that Firefox does. The push towards rapid release cycles in many parts of the software industry seems to be leaving behind the principle of getting it right the first time.Īnyway, that's all the time I have for this nonsense, because I've got a couple of projects of my own with unresolved issues, and I don't want to be a hypocrite. But, people have been complaining for years about performance problems, and IMO there should have been a show-stopping effort to fix it a long time ago, rather than the incremental efforts that, to many users' perceptions, have made little to no improvement. Īnd now for the part that will probably make me really unpopular here: if they fix major issues in an upcoming update, that's great. But, they've also had display bugs around for almost 10 years, and they've banned bug submitters over etiquette issues without actually addressing the bug in question. I was referring partly to Mozilla's responses to the reaction from corporate support people over their forced-updates announcements.
0 kommentar(er)
