51–60 of 124 posts
Earlier quoted context omitted.
Chrome users in general do not use as many extensions as Firefox users, so they have less reason to worry about them breaking.
Do you have any proof of that? I'm genuinely interested.
Mozilla needs to do something to de-dramatize what some people see as version inflation. A lot of people get anxious to see these very frequent bumps because major x releases are associated with add-ons not working, bloat, etc.
What about type rendering? If FF on OSX no longer uses quartz to perform drawing operations, what implications are there for type rendering? Will OSX users be subjected to the (IMO) ravages of freetype? Or will each platform continue to use native type rasterization?
Mozilla needs to do something to de-dramatize what some people see as version inflation. A lot of people get anxious to see these very frequent bumps because major x releases are associated with add-ons not working, bloat, etc.
True, but on the other hand people will get used to it, just like they did with Chrome. The version number doesn't matter, all that matters is that it works. I like to see Mozilla responding. I don't know if development has speeded up, but it seems to have done. If they can keep this up without letting security slip I'll be impressed.
It's good Mozilla is moving forward at a rapid pace (particularly with the memory issues), but as long as the remainder of the software world is still in either the 90's slow release cycle or the 00's everything-is-a-beta-v0.x mindset, Firefox/Chrome will be aberrations.
I may learn to tolerate it, but that doesn't mean I'll get used to it.
Earlier quoted context omitted.
The article said the "dev" channel of Chrome, which is equivalent to Firefox's nightly build, so they are about equal. It just happens that the current nightly channel of Chrome might be released earlier.
It's not the same thing. How is Firefox 7 version called then? What about 6? Does Firefox have 4 modes instead of 3, like Chrome (dev, beta, stable)? Firefox's "dev" mode might be equivalent to "Chromium" mode for Chrome, in which case I suppose Chrome also has 4 modes, but their dev modes are still not equal to each other. The point was that Chrome 13 will become stable in 2-3 weeks from now (an Chrome 14 - beta), a…
Can we assume that the benchmarks mentioned for OSX apply equally to Linux?
What about type rendering? If FF on OSX no longer uses quartz to perform drawing operations, what implications are there for type rendering? Will OSX users be subjected to the (IMO) ravages of freetype? Or will each platform continue to use native type rasterization?
Could you detail what you call the "ravages of freetype"?
Earlier quoted context omitted.
The "conversation" of this thread started with someone commenting on the fact, seemingly surprised and even bothered, that we are already talking about Firefox 8 when seemingly Firefox 6 and 7 went by so quickly we didn't notice it happening. In this context, it is incredibly relevant that Firefox 6 and 7 are still being described in the future tense, as that would imply that they haven't actually been released yet.
Versions 6 and 7 haven't been released yet, but the feature sets are locked in due to the faster major version release cycle. The recently discovered memory fragmentation issues ( https://bugzilla.mozilla.org/show_bug.cgi?id=666058 ) and more efficient garbage collection are being addressed in version 8.
This is pretty crappy. What is the rendering difference of 5 to 8? How many versions am I as a web developer going to have to support. short dev cycles and fast releases like this are stupid.
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.
> Chrome 14 should be stable in about 8-10 weeks. Firefox 8 won't be stable until 14-16 weeks from now. This almost-gripe is such a beautiful illustration of how far we've come in upping the pace of browser tech innovation. Thank you Mozilla (for this round).
They forced pretty much everyone in the browser area to play catch up with them to stay relevant, and the results are really awesome (and not just in release cycle speed).