Linked by Thom Holwerda on Sun 10th Oct 2010 14:17 UTC, submitted by Extend
Permalink for comment 444778
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2010-03-08
Hum, not exactly, in my opinion...
-Hardware acceleration is the last refuge of devs who don't know how to write well-optimized code. E17 shows best how much GPU acceleration is badly overrated, in my opinion. You can make something good-looking, and even pack it with superfluous and hideous eye-candy as a technological demo using raw CPU power and still don't get a single glitch... That is, if you know how to code.
-Resolution independence in OSX and Win7 ? Well, sure, there's a bit of it in there, but close to none. Since when did they make applications (ie most of the user experience) resolution-independent ? Or even provide an API for that ? Since when is input resolution (ie making controls bigger when using an imprecise interface like a touchscreen or a pen tablet and smaller when using a more powerful interface like a mouse) taken into account in their resolution-independence algorithms ?
Edited 2010-10-11 14:08 UTC