Hacker News new | ask | show | jobs
by stan_rogers 5073 days ago
Perhaps, though, this is the kind of kick Adobe needs. Photoshop, for instance, was built on Carbon until CS5, and needed some tricksy memory tampering to keep the whole session from being a swap exercise. (Even on Windows, I've found that if I didn't already know what the dialog contents were, I'd never figure them out half of the time -- the text doesn't fit into the space they've allotted for it, even for single-line legends.)

The features and ecosystem keep me there, but their underpinnings have lagged, and apart from the splash screen (which is now "creative" but butt-ugly), they haven't spent a whole lot of time making sure the GUI works on any machine, let alone on Retina-type displays.

Being able to judge adjustments for print at near-print-size has always been a major hole in the feature set. That's not Adobe's fault—until very recently, there were only a handful of automobile-expensive monitors requiring special interface hardware that could provide such a function—but they should have realized that if the subject ever came up, designers, ADs and photogs would be all over it in a flash. That doesn't take a JREF challenge winner to predict—the phone-sized hi-rez monitor should have been a clue that it was just around the corner. It should have already been in the pipes, even if it wasn't ready for prime time for the launch of CS6.

1 comments

There's little chance this kick Adobe into action. They're moving slower and slower (and subscriptions are a license to snooze). It makes me very worried it will be 3-4 years before CS is in line with retina (instead of 1-2).

FWIW - I don't see how retina can be solved easily: Apple kinda screwed it. Mainly, how do you show 1x pixel accurate content on a device that won't do 1x pixels?