The start of something beautiful.
I have become completely dependent on my computer for all sorts of things. Obviously, I use my computer to develop software, but I also use my computer for banking, email, my personal phone book, my appointment schedule, playing games, and so on.
I am not quite at the point where I leave my machine on 24 hours a day, 7 days a week, but soon I will be able to carry a computer in my pocket during those rare hours my desktop machine is not at easy reach (like when I’m flying back and forth between Seattle and San Francisco). This computer’s official name has not been announced yet, but its codename is Pegasus. It’s being created by Microsoft with six hardware partners. I’ll start by showing you the Pegasus hardware from the user’s perspective. In the second part of this article I’ll dive into the details of the software platform and discuss the programming issues you need to understand to write cool Pegasus apps.
Don’t believe the haters and retrospective I-bought-my-first-smartphone-in-2009-and-now-I-know-everything naysayers – PocketPC was an amazing platform that put so much functionality and awesomeness in your pocket back when Google was still Altavista and Apple had just started peddling music players.
Palm OS may have been my dressage show horse, but PocketPC was my trusty workhorse.
I coded for a Cassiopeia. It wasn’t exactly beautiful, but clearly the best you could get back then.
But let’s face it – compared to what we have it’s pretty crappy.
I can’t recall those functionality and awesomeness of PocketPC devices. What I do recall, is that when I had both Palm PDA and PocketPC smartphone, my usage pattern led to selling PocketPC device and buying a Philips “dumb” phone with good battery and solid bluetooth. This was a huge improvement in my mobile setup. (Unfortunately, Treos were too hard to buy and too expensive at my location back then.)
Edited 2015-02-10 23:23 UTC