To view parent comment, click here.
To read all comments associated with this story, please click here.
If the memory thing is out of date, reply to that effect. An outdated comment is not off-topic, it's out-of-date. You should reply indicating current information. If you can make a point, do so.
Then again, maybe the comment isn't out-of-date. Sounds like meianoite and others have seen reports of continued issues with memory usage. In fact, you imply that work in this area is ongoing, so you can't even maintain the assertion that the issue is out of date for 20 words.
200+ fixed memory leaks is a great thing, and the people who identifed, fixed, and verified these leak fixes should all be proud of their work. However, in the final analysis, a lot of people won't care if leaks have been fixed if the product still uses too much memory.
Think of it this way, would you care if 200+ safety problems had been fixed in the new model year car you bought if the tires still came off at speeds over 62mph/100kph? Is it a good thing that the 200+ safety problems had been fixed? Is the car maybe safe for folks that never have to go very fast? Yes and yes. Is it time to declare comments regarding the car's safety problems out-of-date? Maybe you would think so, but many others would disagree.
How about you try not being a jerk? If it helps, here's a post you might have made instead of silently modding kaiwai down:
RE[2]: Native widgets?
If you look, you'll see that there have been 200+ memory leaks fixed, so there should be some reduction in memory usage already. There are some bigger issues, mainly in memory fragmentation, which [we are | the team is] currently working on. It's hard to say now when this work will bear fruit, but you and other users concerned about Firefox's memory usage should know this is on [our | the team's] radar and that it is being worked on.
See, this way, instead of looking like a total anus, you get your point across. As an added bonus, you make [your | the Firefox] team look like what they are, which is a conscientious group of developers, testers, and others working hard to produce the best damn browser on the planet.
wtf? kaiwai is right about Firefox having memory problems. It still has those issues. It has many memory problems solved, but there are still many left to solve.
Personally I prefer webkit-gtk (the 'official' webkit.org port) a lot more and luckily it's been picking up speed recently.
Kaiwai:
Hear, hear.
Cyclops:
It was definitely not off-topic, given the subject of Firefox 3 nearing golden and still hogging memory as always. Bullet points on a release notes document won't change the fact that FF3b as it stands is hardly an improvement over FF2 in memory management:
http://www.techcrunch.com/2007/11/20/firefox-3-beta-1-the-memory-us...
Given that, my opinion is that despite believing otherwise, you had zero reason to mod Kaiwai down, period. And pretending FF3 is the vessel of the divine blood won't change the fact that modding him down for his criticism is akin to sweeping bugs under the mat: people will trip over them. Specially people with constrained hardware resources. Specially 3rd world governments trying to jump into the eeePC/OLPC/Classmate/whatevercomesnext bandwagon of cheap internet-oriented computers.
According to zdnet memory management is indeed improving (notice that FF3b1 actually beat IE7 by using less memory in the 12 page test).
http://blogs.zdnet.com/hardware/?p=960
Does this now mean you are going to start whining and carrying on about IE7 in the same manner?






Member since:
2005-07-06
Nice to see censorship is live and well, under 5 minutes a point is taken off my score; interesting to see the maturity of some around here is taken to all new pathetic lows. When in doubt, and too lazy to debate, remove a few points to silence the critic(s).
Edited 2007-11-20 19:43