Perfect iPod

27 09 2008

I was in an Apple store having someone look at my charger yesterday. While I was waiting for someone to get to me, I decided to look around the new iPods. While I love the new iPhone OS, I found the prices on the iPod Touch high and the space lacking. I think my “perfect” iPod would be an iPod Touch with a hard drive instead of flash storage. Slap a Toshiba 240GB drive in there with 2GB of flash to provide a cache and sell it at $349. I think it would likely kill the sales of the Classic dead – which is almost certainly the long-term goal Apple has. A

I can dream, can’t I?



Maemo “5″

23 09 2008

I’m getting most of my news second-hand (and third-hand, really) from the inaugral Maemo Summit, but I hear that it went off reasonably well. What I gathered from Ari Jaaksi’s keynote is essentially that a number of my concerns about Maemo have been addressed.

Going back to my Maemo Diablo post that is to date the second most popular post on my blog, I find that a lot of the things on my checklist are at least being addressed. Without seeing the implementation, I can’t say whether my concerns will be alleviated, but it’s nice to know I’m not the only person who wants to see Maemo succeed. So a quick rundown of what I wanted and what we all got:

  • Modest (har har) improvements in email – check.
  • Faster browser – sort of inevitable, really.
  • Where does Maemo stand in a newly, um, FOSS-ilizing company like Nokia: sort of. I’m still unconvinced Maemo is the future of Nokia, but knowing that this is not just a ten year experiment in FOSS is reasssuring. I would’ve liked to hear more about (and maybe I will as news trickles down in the forums and blog entries) how Maemo fits with the entire FOSS “ecosystem” at Nokia, including the new FOSS Symbian stack and such, but I understand why Nokia may be reluctant to talk medium-term plans.
  • Usability – CHECK! Praise the lord and pass the ammunition!
  • UI guidelines/UI excellence – even better, Nokia will help offer UX consulting. I could not ask for more.
  • Application store – check. However, as good as it is that Nokia is offering such a store, it really needs to move aggressively to make the store work. Just today Android’s App Market went live, and that’s three months after the noisy arrival of the iPhone/iPod Touch App Store. Nokia must also be prepared to: (a) publish clear guidelines on what can and cannot be in their application store, so a Podcaster-like debacle cannot happen on the Maemo platform, no matter how well intentioned; and, (b) be prepared to accept lower revenue than they see Apple and others earning from their stores. The simple fact is that this is an open platform that has so far been marketed towards the technorati who are both more willing to look around for a free alternative and willing to build a free alternative if none exists. Nokia cannot loose interest in the store as it has with Download! for the S60 platform, which, in most cases is a moribund pit of piddling links to carrier-specific crap.

In addition, Nokia seems to be dedicating significant resources in making the platform faster, both from a hardware perspective (hello OMAP3, how nice to meet you!) and a software perspective (Upstart, GSTOpenMax, even OHM). There’s also a substantial improvement in store for the multimedia component of Maemo which has been more than a little weak; I prefer to use the term “brutally non-existent”, personally.

Finally, while HSPA is welcomed with open arms, it also makes it harder for me to decide what to do with Maemo. Maemo sits at an uneasy border: it is under assault from the portability side by Nokia’s own ever improving S60 and other superphones* like the iPhone; on the other side – power and functionality – the Intel juggernaut is shrinking the Atom ever faster and bringing the gift of a full, x86-compatible OS down into the same price range and package size. Heck, the Nokia N810 officially retails for more than my brand new and much adored Atom-based Acer Aspire One does, and I have way more functionality in a package that is only about twice the size. So I’m a little confused what the future is for Maemo (going back to my first point about where Maemo sits in the FOSS-adopting Nokia world).

HSPA (and the other improvements, like high-res cameras and better screens) means that in a sense, Maemo is going towards the superphone category. There it faces some entrenched competition: RIM’s BlackBerry, Apple’s iPhone, Google’s Android, Windows Mobile and, of course, Nokia’s own S60, and increasingly, Series 40 platforms. Quite aside from whether Nokia is ready for a potential civil war between its Maemo and Symbian divisions, time is short for Maemo to be in that market as a major competitor.

It remains to be seen what the future of Maemo is. For me, though, I suspect this is the end of my Maemo line. I loved – and still do adore – my spunky little N800. However, given the coming processor switch and the need for new hardware, unless Maemo 5 makes it back to the N800, I will not be buying a Maemo 5 device. For me, and I fear many others, the calculation looks a lot like this:

  1. Buy a Maemo 5 device for about $400. I duplicate the functionality of my phone with the HSPA, but I don’t gain the ability to run a full x86 OS.
  2. Buy an Atom-powered netbook for about $400. I don’t duplicate the functionality of my phone, and I get the ability to run a full x86 OS – like Windows.

Given these choices, it’s pretty much a no-brainer: you go with the Atom-powered notebook. If the Maemo 5 device was cheaper (say, $200), then it’d be a much harder decision, but given the history of Maemo, that is unlikely. One last option is that Nokia sees Maemo 5 as a media device. As a media device, especially one that is advertised as being able to browse the web, it might yet be a device worth the money. Cram it with 32-64GB of memory, give it a decidedly media-centric feel (including dedicated play/pause buttons), the ability to download music and movies on the go (no bloody tethering needed) and Nokia could go head to head with the likes of SanDisk, Microsoft and Archos. At the very least, it would shake up the market, since as beloved as Apple is, Nokia is a much, much bigger brand in most of the world.

So: better clarity what the future of Maemo is in the short to medium term. Long-term however, I’m still scared for the platform that has travelled nearly a quarter of a million miles with me around the globe.

*: A superphone = a phone that can be conceivably used without needing to be teethered to install apps. I’m aware of the music limitations on the iPhone, and quite frankly, that’s data and not applications. The App Store works perfectly over EDGE or WiFi.



Vinge – Deepness Series

22 09 2008

In my continuing romp through classic and modern must-read sci-fi, I’ve returned to read Vernor Vinge’s A Fire Upon the Deep and A Deepness in the Sky. While ostensibly these are standalone books – and you can certainly read them as such – reading them together will considerably improve your understanding of the universe in which the two stories are set.

While A Fire Upon the Deep was published before A Deepness in the Sky, in the Deepness universe, the latter precedes the former by about 20,000-30,000 years. Thus, if you read it in publishing order, you’re likely to find the second book very limiting in scope. Unlike Rainbow’s End, A Fire Upon the Deep is definitely stuck in technological history – newsgroups are the primary way of conveying information back and forth. A Deepness in the Sky, by contrast, nicely abstracts away the information carrying mechanism and focuses (pun intended) on the slavery involved in generating said information. I should also note that the story of A Deepness in the Sky is much richer and triggers much more introspection than that of A Fire Upon the Deep, where the moral ambiguity seems forced.

Briefly, the chief plot driver is the layout of the galaxy. In order of increasing distance from the galactic core, the four zones are the “Unthinking Depths”, the “Slow Zone”, the “Beyond” and the “Transcend”. The origin of these zones are never really explained, but the consequences for inhabitants of the four zones are considerable. As their names suggest, the closer one is to the galactic core, the less sophisticated the technology available. Indeed, a major plot in A Fire Upon the Deep is a 6000 parsec race across the galaxy through the zones to stop an Voldermort-esque terror.

I have to say that, as with Vinge’s Rainbow’s End, I had considerable difficulty accepting this basic premise. To me, as an amateur astronomer and astrophysicist and someone who measures civilization by the Kardashev Scale, I would expect more advanced civilizations to harness the biggest, most energetic power source in the galaxy: the supermassive black hole at the center of our Milky Way. Conversely, an intelligence at the edges of the Milky Way is likely to be starved for power once it exhausts the resources of its home system and would logically expand towards a star- (and hence, energy-) dense region of the galaxy: closer to the core.

There are a number of popular interpretations for this sort of inverted power structure. The argument that I’ve heard that is most persuasive to me is that Vinge is interpreting the galaxy like a black hole – the closer you are to the singularity at the center of the black hole, the more time is stretched out. In some fashion then, the closer you are to the Unthinking Depths, the longer it takes for anything to happen, and the more distortion there is on your vessel. It’s not the most elegant argument, but … I can see some sort of logic behind it.

Unlike Rainbow’s End, where Vinge has either written rather more fluffily or had an editor who cut ruthlessly, A Fire Upon the Deep has certain passages that make Virginia Woolf seem readable. I confess to having struggled to get into the novel several times before I make it past the crash landing on a world close to the Slow Zone. Perhaps because the story is less expansive or because Vinge had a better editor for A Deepness in the Sky, I found it to be his best novel yet: fascinating without bogging a reader down in needless detail. To be sure, Vinge glosses over certain things – many practical aspects of interstellar life, in matter of fact – in a fashion that makes me cringe and long for Alastair Reynolds’ no-nonsense style, but all together, I found the two books more interesting than Rainbow’s End.

Unfortunately, there is a major risk in reading anything after Charlie StrossAccelerando: no matter how wacky the technology, it always seems rather tame and evolutionary rather than mind-blowing and revolutionary. And certainly neither of these books pushes the state of the art in technology; in fact, reading the newsgroup postings in A Fire Upon the Deep, I felt that it was a rather genteel and quaint time for high technology.

What’s most important for me about these books, though, is the terminology he introduces. For example, it becomes clear about a third of the way into A Deepness in the Sky that despite 15,000 – 20,000 years of technology, contemporary human computers in the novels still rely on the Unix epoch to determine time. Another instance is his use of ten powers of seconds to tell time – hours are 3.6 Ksec, a day 86.4 Ksec, a week is .6 Msec, a month 2.6 Msec and so on. Driving to a restaurant after reading the novel, I found myself calmly noting that the road had been repaved in the last few Msecs.

To sum up: A Fire Upon the Deep is an interesting and thought-provoking book, but the story seems contrived and the pace forced. I’m going to make a prediction: you are going to find yourself frustrated by the vastness of the story and the need to rush through the plot quickly in order to finish it in a reasonable time (a few hundred Ksec maybe?) However, A Deepness in the Sky is a book worth reading a couple of times – all 750+ pages. I found the story of A Deepness in the Sky both more interesting and better thought-out than its predecessor. It’s a great and persuasive vision and one which creates a plausible scenario where even the most determined abolitionist might consider slavery an acceptable choice.



All Synced Up (part 2)

11 09 2008

One of the things that I’ve been after for a very long time is the ability to have my calendar on any device or software, and have them all in sync. The path to this synced up nirvana has finally been reached, albeit, not the way I expected, in all honesty.

If you remember, when I last explored this topic, I had to sync Google Calendar with: an Ubuntu machine with Thunderbird and Evolution, a Windows machine with Thunderbird and Outlook, a Windows machine with Lotus Notes, a Mac with iCal, Thunderbird and Entourage, a Nokia N80, a Nokia N800, and I’m sure I had a half-dozen other devices in mind. I can’t remember.

Since then, the simplification has occured. To wit – some machines replaced, others discarded, others are no longer necessary to sync. So this is how I do actually, somehow, manage to keep my calendar in sync.

  • Windows machine, with Thunderbird: Lightning + Provider for GCal.
  • Windows machine, with Outlook: Google Calendar Sync.
  • Windows machine, with Lotus Notes: custom code that converts iCal into Notes events and vice versa.
  • Mac – retired and up for sale.
  • Ubuntu machine, now Thunderbird only: Lightning + Provider for GCal.
  • Nokia N80 – replaced by iPhone.
  • iPhone – NemusSync.
  • Nokia N800 – retired for the now; maybe resurrected.

Within at least a couple of hours, thus, I am entirely in sync. NemusSync for the iPhone does not have background sync, though I’m beginning to suspect that this may be solvable with a cron job. Either way, I’m really enjoying being able to add an item into the device that is handiest and having it appear (magically!!) elsewhere, and sadly, it’s only taken years to get here.

What we really need is a generic sync protocol for arbitrary data, kind of like IMAP for email. In fact, if there was a way to explain capabilities in the sync, it would be even better. It would be cool beyond words if you can arbitrate different data formats in the sync; imagine never having to transcode files a thousand times – do it once, and the underlying sync protocol will do the rest. (Side note: I wanted to call it OpenSync, but apparently, that’s taken.)



Why Linux

4 09 2008

Lifehacker, a favourite around these parts, has two articles up about why their readers switched to Linux. Some of the people switched for ideological reasons (Microsoft’s asinine “Genuine” program comes to mind), some because they wanted to use older machines, and others out of simple curiosity. I came because I was curious, and the more that Microsoft turned the screw on “pirates” the more I wanted out.

Unfortunately, there is one major stumbling block to my adopting Linux entirely: Office. While I’d like to say OpenOffice is great, it isn’t; frankly, OpenOffice is awful. I spent almost two weeks trying to get my resume to look the same in OpenOffice as I did in Office, and somehow, it just didn’t work out. I have a pretty crammed resume, to the point that every line and line space counts. Unless I shrunk, on average, every font by about two points, I was simply and utterly unable to get the same amount of content on my page. I’m not sure why this happens – particularly if I have exactly the same margins and kerning as in Office; I suspect there is something different in the underlying structure of OpenOffice’s renderer and it is this that causes me to stick to Office. Even documents produced natively in OpenOffice just don’t quite look right when printed. Again, I’m not sure why – but I find that often Google Documents looks more correct to me.

Being forced to use Office means: (a) Windows; (b) Mac OS; or, (c) years of my life configuring WINE to run properly. It’s not a happy choice, but I’d like to use Linux and other free alternatives more; where I can, I do. I run FreeNAS on my home server, I run Linux on an older laptop, I run OpenWRT on my WiFi access point. These are all incremental steps towards a free and open computing experience, but I hope for a better OpenOffice, so my main machine can also one day run Linux.