Skip to main content

Why PCs Do Not Make Good Gadget Makers

I think this CNET story hits it on the head: "reality still trails Microsoft's ambitions"

I will say - I was very excited about the potential of Origami, a light-weight device that was as functional as a regular laptop but designed for hand-held use. An intelligent user interface, much like the one that appears to be happening with the Origami Program Launcher would be welcome for many businesses and end-users. But PC people who keep on thinking that users (even though this one is very positive about it) will shell out big bucks for these devices are just out of their heads.

It killed me this year to have to shell out over $600 for a mobile phone PDA when my original Blackberry only costs $189. Yea, I know Microsoft wanted to make the device under $500 - but just like Apple's Newton (which was similarly overpriced), $800-$1100 (for Samsung's Q1) is just way to ridiculous. Even if they had managed to offer ONE that was under $500 (as they did with the xBox), they could have saved some face.

But it did tell me one thing: I have no reason whatsoever to look at a Tablet PC. So with one swoop, MS managed to kill two products at once. The Tablet PC is still overpriced and now, they come out with this device which makes laptops even more attractive. Maybe even three if you consider that the Portable Media PCs may be a little cheaper but far less functional. And it's not even Microsoft's own.

Now don't get me wrong - I would love an Origami device but at that price, Microsoft has just opened the door for a company who does understand gadget pricing ( and one that reminds me I need to eat some fruit today ) and now runs on the Intel platform to really shake up the world of portable devices. Or maybe someone else.

Too bad.

Reality check for the much-hyped Origami PC | CNET News.com

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...