Quote:
Originally Posted by DavidinCT
As I 100% agree with the fact that Windows ME was the biggest piece of crap Microsoft ever made (besides Microsoft Bob), I am in IT and I used to call it Windows Ass (not kidding).
I think it will be hard to compare WIndows Phone 7 with Windows on the desktop and you comparing "7" phones does not fit at all. Windows support millions of different types hardware (video cards, scanner, harddrives, CPUS, printers...should I go on ?) mobile phones should not.
Again, another problem with Windows Mobile/PocketPC, OEMs where allowed to do anything here too. Microsoft only sold licences to PocketPC, allowing OEMs to create what they wanted within some minor guide lines.
So, you will get a super powerfull phone and others ran like crap because a OEM wanted to make a cheaper devices. Some oddball hardware with poorly written drivers, caused major problems. Over the years, it has spawned a little out of control, some nice features but, not gobal on all models so, if the other OEM came out with that feature, it might need to recreate the driver needed and there comes problems.
Microsoft wants to control the hardware and the software to keep up quality control and sad to say, I 100% agree, again as long as it's done right and fair for programmers (MS needs to do this, a Device is only as good as it's apps and WP7 is starting over).
Not trying to go off topic too much here but.... Do you know why Apple products work so well ? Why they always run smooth and seem really quick for what they are ??
Apple designs, programs, manufactures, packages and markets their own products. I have always said, if Microsoft made their own computers, designed in house, they would be the ultimate computers.
Same with phones, they can't make the hardware but, they can take control on how it's done. By doing this, they can attempt to get it right this time.
I've been a WM user from PocketPC 1.0 and have seen the problems over the years, that is why I think this is a good idea, at least try it.
Just my 0.02.....
|
I'm all for standardizing minimum requirements for hardware and some of the other things you mentioned, but you can enforce most of that with a modification of the licensing agreement you require the hardware vendors to accept before they can build devices with your OS on it. Microsoft didn't have to close the WP7 platform, that was too excessive in my opinion. This isn't supposed to be a gaming system, which has always been closed platform, it's supposed to be a business class phone that does other things, which used to be an open platform. I pay about $36,000 a year, every year, to Microsoft for a Campus Agreement. How about throwing me a bone, and allow middle states accredited schools and enterprise level customers a waiver and access to native mode so that I can do my job properly.
I too work in IT and if I want to make a SQL front end app for my proprietary CRM systems , I shouldn't have to break FERPA regulations exposing my data unnecessarily while Microsoft looks through my companies code to "approve it", before I can run it on our mobile phones. I also don't want MY app in the store so that other people can buy/use it either. We've been waiting forever for HTC and other companies to break installing crappy 400-528 MHz CPUs in their phones for years, only to finally start seeing SnapDragon and Hummingbird CPUs but then neuter the OS that business class customers want and need to run their business efficiently.
What is with technology companies all of a sudden taking 2 steps forward, and then 10 steps back?
07-29-2010, 11:53 AM
MOBILE 7 FAIL Reply
Hybrid Mode
