Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by wmf on Monday July 11, 2011 @09:55AM
(#2750648)
AFAIK Firefox still uses Quartz; in fact it's now supposed to be Quartzier with less Cairo overhead.
Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by idan on Monday July 11, 2011 @05:17PM
(#2752551)
RTFA: "Azure removes the Direct2D and Quartz (OS X) go-between and allows Firefox to write directly to the underlying 3D subsystems (Direct3D and OpenGL)."
Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by thristian on Tuesday July 12, 2011 @01:23AM
(#2753647)
That seems like a journalistic misunderstanding; I'm pretty sure Azure is designed to replace Cairo as the layer between Firefox and Direct2D or Quartz.
Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by illicium on Monday July 11, 2011 @08:04PM
(#2752994)
Maybe for WebGL, not plain page content.
Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by jbk on Monday July 11, 2011 @09:48AM
(#2750624)
Could you detail what you call the "ravages of freetype"?
Re:Firefox 8 is 20% faster than Firefox 5, matches Chrome 14
by oldpatricka on Monday July 11, 2011 @10:04AM
(#2750697)
Diffeent platforms use different font rendering algorithms. I'll avoid saying that one is better than the other, but it's off putting to see one rendering alongside another on the same display. Apple got into trouble with this when they ported Safari to Windows, and used OS X font rendering on that platform.
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?