naoru

Offtopic, but this is very interesting. I have this sort of problem as well, but with color rendering. Not on a Sony, but on a Philips (50PUT6400). Makes me think that they might use a common platform for their entry-level TVs.

Based on title I first assumed that this is about signal processing, but then came the disappointment.

Developing for IE6 by itself leads to PTSD.

And there's this thing: http://www.windows93.net/

So it's a PenTile display [0].

[0] https://en.wikipedia.org/wiki/PenTile_matrix_family

Das Keyboard [1] makes you value your keyboard shortcuts (and time) much more. Keyboard is an interface for hands, not for eyes.

[1] http://www.daskeyboard.com/daskeyboard-4-ultimate/

I was expecting a big "NO".

I've got two rMBPs from 2012, one is 15" (with the infamous LG display, retentiongate anyone?), the other is 13". 15" is heavy used and has some marks from the keyboard on screen, but coating is intact. 13"'s screen is in nearly perfect state.

No "staingate" at all. Sure, there are many other gates like magsafecrapgate, yosemiteslowgate, unbearablyslowgraphicsgate and such. But no staingate.

Or you can raise suspicion, get caught on surveillance camera and have a talk with a police officer. Yeah, there might be ways to avoid that, but in case of failed attempt there will be one more thing to explain.

Oops, Tweetbot is kill. Something something API limits developer love walled garden.

Why? Stuffing a computer in a mouse makes no sense, you'll need a keyboard anyways, so why don't you stuff a computer in a keyboard? Oh wait, somebody did this before. Bummer.

Yeah. Just look at this menu bar when switching focus from internal Retina display to external non-Retina ATD. http://cl.ly/2W172H0l3s0z This bugs the hell out of me.

Not so long ago I grabbed myself a G4 MDD with 768M of RAM — it was much more responsible in terms of UI. 3-4 browser tabs slowed it down though, while my current rMBP13" from 2012 works ok with a lot more.