Archives June 2010

Two years ago I wrote about what Microsoft needed to do to turn their platform around.  Now with Windows Phone 7 only months away, it would appear Microsoft has failed in every way imaginable.

Windows Phone 7 will be a miserable failure.  There are many countless reasons why it is going to epic fail, but here are some of the most important:

1) Microsoft doesn’t know mobile phones from a hole in the ground.  Just look at the current state of Windows Mobile.  It’s built on the Windows CE platform, created in 1996.  Yes.  Let me repeat.  Windows Mobile is based on a platform created in 1996.  Sure, the platform has seen updates, but it’s still based on a world created 13 years ago.  Back when Windows 98 was nothing but a dream.   Windows Phone 7 is based on Windows CE.  Yup.  Microsoft’s newest “cutting edge” Phone OS is STILL based on Windows CE.  They just couldn’t get rid of it.  Thanks Microsoft.  The same bullshit you’ve been jamming down our throats for the past how many years that has NEVER worked right is your platform for the next Windows Phone?  EPIC FAIL.

2) The Kin is a disgusting failure.  The Kin is running a hacked down version of Windows Phone 7.  Don’t believe me it sucks?  Here are a few quotes regarding the Kin and it’s abilities:

“…Lofty goals indeed for a product like this, and unfortunately for everyone, Microsoft misses the mark by a long shot. It’s not even close.”

“…we also take issue with the browser, which is abysmally slow and buggy (it consistently crashed while trying to load any complex web pages like Engadget), and the email client, which seemed to have trouble displaying even the most rudimentary HTML messages”

“While using the One and Two we found ourselves consistently confused or surprised by how many bad little interface problems there are. Not only does the phone make it hard to do simple tasks — and not only are the social networking features poorly implemented — but the handsets are often sluggish, hiccupy, and downright crash-prone. We were told by the devices on more than one occasion that we needed to restart (while performing basic tasks), and often it would just throw us a blank screen while we waited for the device to come back from whatever tragic internal situation was occurring”

That’s enough of that.  If you want to read more though, you can head over to Engadget’s review of the Kin One and Two.

Read More

I was setting up some brand new HP Probook’s today (typically VERY nice machines in my experience) when I was suddenly rendered crippled by a IMPOSSIBLE to use touch-pad.  What a DREADFUL piece of shit this new design is.

Basically, the touch-pad and buttons are all one surface.

Observe:

The problem comes from the fact that the “button area” is still part of the touch-pad.  So you place one finger on the button, and now you can’t use the fucking touch-pad.  Your cursor will either sit there and stare at you like a vegetable or it’ll jump all around the screen like crazy.  Either way, the touch-pad is completely unusable if you’re touching either button.  This is incredibly frustrating because my style of laptop mousing is resting one hand’s fingers on the buttons while using the other hand to navigate the mouse, or resting one finger on the button, while the other navigates the mouse for faster mouse action.  The only effective way to use this touch pad is with one hand and one finger.  Christ.  It’s awful.  Seriously.

I ended up grabbing one of those USB ball mice and plugging the damn thing in and using that, because trying to use that bloody touch-pad was making me want to kick puppies.  And I love puppies.

Thanks for the SHIT design HP.  I’m sure as hell glad this isn’t my machine.  I would be returning it if I had to put up with that damn thing.