61–70 of 124 posts
Earlier quoted context omitted.
Zero crashes, zero manual restarts, zero lag.
And addon support?
[1]: https://addons.mozilla.org/en-US/firefox/addon/add-on-compat...
So then Firefox will still be behind Chrome? Firefox 7 will be the one launched in the same time with Chrome 14. Chrome 14 should be stable in about 8-10 weeks. Firefox 8 won't be stable until 14-16 weeks from now. That's around the time Chrome 15 will be out.
I continue to be confused be what I interpret as "version number envy". Are people really that impressed by version 14 vs version 7? If FF7 is awesome, Chrome 14 must be x2 awesome! Is Firefox development "behind" because of version numbers? I'm most surprised that Mozilla seems to take this so seriously. Are the numbers anything other than a marketing / PR game? Any reason either side couldn't arbitrarily jump to ve…
I might go back to Firefox when it no longer consumes gigabytes of RAM after a few hours of operation. Until then, I'm with Chrome. I don't care about speed as much -- so long as it's reliable, and doesn't grind the rest of my machine to a halt, it's all good.
But for my usage patterns; with many tabs opened after a few hours of operation, Firefox consumes less RAM for me.
Also, don't confuse memory waist (coming from bloat and fragmentation) with memory used for improving the browsing experience, like caching. These browsers are doing a lot of caching and I personally don't like having 4 GB of memory and being left unused.
I might go back to Firefox when it no longer consumes gigabytes of RAM after a few hours of operation. Until then, I'm with Chrome. I don't care about speed as much -- so long as it's reliable, and doesn't grind the rest of my machine to a halt, it's all good.
Chrome is very wasteful; only after many hours of operation in which you opened and closed dozens and dozens of tabs, it starts to be better than Firefox; as Firefox fragments memory and doesn't release it properly when closing a tab. But for my usage patterns; with many tabs opened after a few hours of operation, Firefox consumes less RAM for me. Also, don't confuse memory waist (coming from bloat and fragmentation)…
Earlier quoted context omitted.
6 is in beta now. Nightlies were 7.0a a few days ago, but if you update.... yep, 8.0a1 PS. Nightly has been incredibly stable on my Mac. I actually use it in production, for no other reason than I was testing it and have no reason to get an old release since it's never crashed and is incredibly fast.
Can echo that Nightly (8) is very stable on Windows, too.
For the relatively simple canvas rendering I'm doing, I can watch Firefox chugging along at 10fps struggling to render a few dozen filled rectangles, while Chrome is happily pegged at 60fps (via RequestAnimationFrame).
It's just night and day.
Firefox 8? What happened to 6 and 7? I see 7's mentioned in the article, but there's not hide nor hair of Firefox 6.
FF6 is in beta, should be out by the end of summer (or early autumn), FF7 is in alpha and should be released before end-of-year. I guess FF8 (which just arrived on the nightly channel) will be up for release in late 2011-early 2012.
(This should be very familiar to anyone who has seen Chrome's update schedule, which has three versions in flight at once, staggered by the same six-week intervals.)