PalmOS or WM -- Palm was always crap
Firstly, my experience with PalmOS after 4.x has been horrendous. The version of Garnet (5.7, I believe) included on the LifeDrive was crap: couldn't switch between Bluetooth and WiFi networking without crashing (timer.c, blah blah,) sanctioned applications would crash regularly, Blazer is just a giant PoS, and I will refrain from detailing VersaMail pains.
Now, move on to the Treo with PalmOS. EVERY single person to whom I provide service complains about the phone crashing, locking up, synchronization problems, Bluetooth issues, and so on.
Putting the two together, I decided that perhaps PalmOS was the culprit and that a WM-based Treo would be better. Unfortunately, no such luck. After recommending Palm WM phones to several people, I was disappointed to find that they suffered crashes, lock-ups, networking issues, and, most annoyingly, schizophrenic Bluetooth.
But who to blame? Given the LifeDrive fiasco and later experiences with the T5 and T|X, I point squarely at Palm and its shyt OS -- one crashed application brings down the whole phuqn machine? That crap went out with the Atari ST, Amiga, and Mac.
But then the mobile phone introduced a whole new playing field: system software modified by Palm, firmwares then further modified by carriers, or so the story is told. Palm blames Sprint for the mangling of its beautiful Treo 700wx WM5 software, and Sprint blames Palm for doing the mangling in-house using Sprint specifications and requirements.
Irrespective of the finger-pointing game, we tire of phones which crash and lock up and do not function as promised. I have had great experiences with HTC phones (other than on Alltel, on which reception is horrible,) Sony Ericsson (love my K790a, even given its functional short-comings, it has rarely locked up or crashed,) and I hear great things about Nokia.
Paris, detailing the pain of poor reception (why does she never call back?)