i won't be flashing my credentials and work experience (anyway, kdarling beats me to it : ), but yes, i'm a developer with a background in real-time applications and limited resources, so i'll just chime in with the following:
- the author of the article from the OP clearly knows what he's talking about. which is: thinking of a mobile in desktop terms is short-sighted, to put it mildly. piggybacking and doing your job in the little windows when you're given green light by the system is the way many real-time, mission-sensitive environments work.
- the people who are crying so loudly about 'being restricted' on their mobile devices fall mostly into two categories:
- nerds who don't use their devices for much useful work but tinkering and showing off, 'look, ma, i can run IM on my phone!', while keeping their mobiles in the charging cradles most of the time, hence caring little about the device's reliabillity in its primary functions (again, the concept of mission-critical devices is apparently foreign to those).
- developers with predominantly desktop background: 'i can clog memory and waste ridiculous amouts of cycles on desktops, apple are evil for not letting me do that on a phone! look at WM and android - they're doing it right!'. first, if WM was doing it right then how come the pocketPC is not ubiquitous today - it's been around for ages, carrying around the desktop paradigm, and even playing a phone sometimes! second, android is a non-tangible platform, before we declare it as 'the right thing' maybe we should, well, see it first in action?