I saw that book, but I don’t feel like learning another API, especially one that doesn’t have widespread use.
The other thing is, I like to avoid higher levels of abstraction if I can. This is just a matter of taste, but I find it frustrating that when you code to a high level API, it’s almost a given that it will be revised and I’ll have to learn a new way to do something I could already do. Sometimes I wonder if the development time is really shortened that much if you factor in the time learning the API. But there’s an appropriate context for everything.
The other thing is, having read about guys who made games for the NES, Atari and other early consoles, I was fascinated by the kinds of tricks and optimizations they came up with to squeeze every ounce of performance out of the hardware. I like to think that the Android/iOS platforms offer a similar opportunity for finding interesting ways to get good performance out of a mobile platform.
© Imagination Technologies Limited. All rights reserved.
Privacy Policy – Terms & Conditions – Trademarks – Cookies