My first cellphone was a
Sony-Ericsson T-300 that I got the summer of 2003, right after I started my first full-time job. I remember wanting the T-300 because it had the neatest feature, you could plug a camera into it and take pictures. (I know, right.)
My second and current cellphone is a
T-Mobile Dash (a rebranded HTC Excalibur) that I got around New Year's 2007. It far outstrips the T-300 in every way, and even though it needed a new battery in 2008, it's held up very well.
(My third and backup phone is a $30 Motorola AT&T GoPhone from Wal-Mart that I keep around just in case. I rarely use it the thing, and those stupid AT&T commercials where the mom chastises her sons about new and old minutes really pisses me off, because roll-over minutes only work if you don't let the account expire. I lost over $100 worth of minutes last year when I let my service lapse, and I've also lost several months worth of minutes this year too because I was a day late using the card I got from Wal-Mart. But I digress...)
Lately, though, I've been thinking more and more about getting a new phone.
This report, of which I've only read the highlights, has got me thinking about it even more today. The thing of it is, I don't really want a new phone, because I don't really like phones.
I got the Dash because I really wanted mobile web access, and the T-300's
WAP-only browser wasn't cutting it any longer. On the Dash I have IE and Opera, and they both do a good job of letting me get around. However, neither of those comes close to the web experience I have when I use my Eee PC. That gives me Firefox, IE (if I want), and specialized widgets for specific web tasks.
Plus, and I know I've said this, you can't write software on a phone. Not easily anyway. I've seen people load Python on Nokia phones, Google has
Simple for the Android, and I've put
SmallBasic on my
Zire; but all of those seem to pale compared to being able to run Komodo on my Eee, using it to write Perl, PHP, AutoIt, or shelling into another system to vi files, all from a keyboard. I can't see a phone ever being as developer-friendly as a netbook.
That's why, even though my Dash is showing its years...namely, its browsers have almost no JavaScript functionality...I don't really want an iPhone, a Pre, or a Droid. I can see the benefits of these gadgets, I imagine I will end up getting one so I can develop for it eventually, but for personal use, it's not a priority. I think Cory Doctorow
said it best: For me, right-living is the 101-key, QWERTY, computer-centric mediated lifestyle. It's having a bulky laptop in my bag, crouching by the toilets at a strange airport with my AC adapter plugged into the always-awkwardly-placed power source, running software that I chose and installed, communicating over the wireless network. I use a network that has no incremental cost for communication, and a device that lets me install any software without permission from anyone else. Right-living is the highly mutated, commodity-hardware- based, public and free Internet. I'm QWERTY-Amish, in other words.
I'm the kind of perennial early adopter who would gladly volunteer to beta test a neural interface, but I find myself in a moral panic when confronted with the 12-button keypad on a cellie, even though that interface is one that has been greedily adopted by billions of people worldwide, from strap-hanging Japanese schoolgirls to Kenyan electoral scrutineers to Filipino guerrillas in the bush. The idea of paying for every message makes my hackles tumesce and evokes a reflexive moral conviction that text-messaging is inherently undemocratic, at least compared to free-as-air email. The idea of only running the software that big-brother telco has permitted me on my handset makes me want to run for the hills.
Right now, as shiny as all the post-iPhone Smart Phones are, I just don't really want to spend money of something that has fewer features than something I already have.