News for hackers. Stuff that matters.
Re:Why 960 x 640 by modeless on Monday April 19, 2010 @06:33PM (#1278052)
A 1.5x scale factor would make existing apps look terrible. They will look fine scaled 2x. If they increase the resolution (and they will; the recently leaked prototype is irrefutable proof) they must increase it 2x for this reason alone.
Re:Why 960 x 640 by algorias on Monday April 19, 2010 @06:48PM (#1278087)
Exactly. Doubling each dimension of an image is a cheap operation. Multiplying by 1.5 is not, due to the antialiasing that would be required. Even with aa, the scaled image would look worse than the original.
Re:Why 960 x 640 by WildUtah on Monday April 19, 2010 @08:57PM (#1278298)
1.5x is a nightmare on Android requiring me to get artwork done twice for every single asset. 2x would be a typical Apple brilliancy--make things easier by using quality hardware. On the other hand, I can see them telling devs to update or get left behind.
Re:Why 960 x 640 by mortenjorck on Monday April 19, 2010 @08:21PM (#1278238)
1.5x would indeed look bad for "legacy" apps, but I think even this fits in to Apple's current developer strategy: Update or get left behind.

I mean, remember, Apple was willing just recently here to risk the incredible backlash of 3.3.1 for the sake of platform direction. I think they'll gladly risk developers complaining about redrawing UI bitmaps.

Re:Why 960 x 640 by mattparcher on Monday April 19, 2010 @10:02PM (#1278380)
I think 3.3.1 is primarily a developer issue, whereas resolution is very much a user-facing issue as well.

With the iPad, Apple didn't force developers to recode their iPhone apps, instead it allowed the older apps to run at native or double resolution. Granted, the double resolution doesn't look pretty, and Apple is strongly encouraging developers to produce iPad native apps, but they definitely seem to be taking advantage of their 185,000 app head start, and 1.5x would presumably look even worse on an iPad than 2x.

Re:Why 960 x 640 by zmmmmm on Tuesday April 20, 2010 @01:01AM (#1278689)
> I think even this fits in to Apple's current developer strategy: Update or get left behind

That seems like the opposite of their developer strategy to me. They've resisted making any substantial changes to the basic hardware profile of the iPod Touch / iPhone lineup ever since it was released, presumably to save developers from having to target multiple devices (and this is still a point raised as a complaint against android all the time).