{"id":1253,"date":"2011-07-07T15:36:53","date_gmt":"2011-07-07T20:36:53","guid":{"rendered":"http:\/\/techcitement.com\/?p=1253"},"modified":"2011-11-17T22:07:40","modified_gmt":"2011-11-18T04:07:40","slug":"why-im-not-typing-this-on-a-touchpad","status":"publish","type":"post","link":"https:\/\/techcitement.com\/hardware\/tablet\/why-im-not-typing-this-on-a-touchpad\/","title":{"rendered":"Why I’m Not Typing This On A TouchPad"},"content":{"rendered":"
I love HP’s WebOS. I love the smooth multitasking, the great apps, the PIM solutions, the card metaphor, and pretty much\u00a0 everything else. It’s easy for me to talk for hours about how great the platform is and how it deserves wider attention. I can pontificate about having actual access to my filesystem and being able to load apps however I like. You can expect to find me waxing lyrical about HP embracing the Homebrew community. People complaining that the tablet is “heavy” are quibbling. I can even talk about how the fact that there are less apps means there’s a lower signal-to-noise ratio. What I cannot do, however, is use one. The problem is not the lack of apps, but the way HP has chosen to handle apps released for non WebOS 3 devices.<\/p>\n
You see, WebOS apps used to be coded using Mojo<\/a>. For WebOS 3.0, HP is switching to something called Enyo<\/a>.\u00a0 WebOS 3 can run Mojo apps, but frustratingly does so in an emulation window of a Pre. Yes, you get the gesture area that’s lacking on the Touchpad, but you also get a ton of blank, wasted space.<\/p>\n