Skip to main content

MS and the PocketPC

For that matter, I have to gripe about MS some more. I use a Pocket PC and wanted to search for news yesterday. As soon as I directed my browser to MSNBC.COM, it immediately took me to a "pocket PC friendly" site. No problem there except that you can't read any of the news - just the headlines and you can't even search.
 
To make matters worse, I tried to see Ken Levy's email letter: http://msdn.microsoft.com/vfoxpro/letters on my Ipaq. Where did it take me to? A "Mobile device" friendly page that wouldn't let me read the letter.
 
I have no problem with web sites that offer friendlier views of the same information but DON'T LIMIT what I can look at.
 
As a result for my news search, I ended up going to CNN's web site.
 
Now, don't tell me that the PocketPC is an "old-hat" product, blah, blah, blah. Yes, I know more resources are going into the TabletPC (which as far as I know still can't be fit into a pocket) or into the Smart Phone (which is effectively PocketPC on steroids). The point is that if they want to promote these technologies as viable, they have to STOP limiting what people can access with them. Tell them it may not look right (and allow me to turn that warning off) but let me get to the information I want to see. (in some ways, technological censorship of this kind is worse than real censorship because you aren't being TOLD you can't access the information - you're just left to feel it's simply not important.)
 

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

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...