News for hackers. Stuff that matters.

A comment on MacBook Pro Retina Display Analysis. Parent comment

Re:MacBook Pro Retina Display Analysis by jonhendry on Tuesday June 12, 2012 @01:12PM (#4101496)
I would probably look at apps other than Chrome. There's "unaware of the retina display", and there's "we eschewed native APIs to some extent and rolled our own implementations of stuff".

I don't know if this is the case, exactly, with Chrome. I'm just saying it might not be wise to generalize from Chrome's appearance to retina-naive 3rd party apps in general.

[ Parent | on HN ]
Re:MacBook Pro Retina Display Analysis by lloeki on Tuesday June 12, 2012 @01:23PM (#4101571)
> I don't know if this is the case, exactly, with Chrome

As part of its security model, Chrome does something akin to rendering everything offscreen in an unprivileged process then passing that to the user-facing process.

[ Parent | on HN ]
Re:MacBook Pro Retina Display Analysis by jonhendry on Tuesday June 12, 2012 @01:35PM (#4101653)
Yeah, that sounds like it would do it. On the bright side, maybe they just have to double their offscreen buffer size.
[ Parent | on HN ]
Re:MacBook Pro Retina Display Analysis by rbanffy on Tuesday June 12, 2012 @05:35PM (#4103028)
Actually, since it's 2D, they have to quadruple it.
[ Parent | on HN ]