[Windows Phone 7 General] N8ter:
Then you're completely missing the context of my posts. Look at what I was replying to then read my reply.

The drivers are a major issue on Android and they have much to do with the updates, or lack there of, or lack of speed thereof...

When a kernel update breaks drivers and makes the phone unusable as a phone or smartphone (due to no Phone or Internet/WiFi functionality), releasing that update is stupid. The skins are easy to port. The drivers are harder and require much more rigorous testing. This is the case whether an OEM is going from skinned to skinned in the update, or skinned to stock to somehow try to lower development and testing requirements...

The Android community is convinced that the skins are the issue, when the skins are fairly easy to port. It's the way Linux breaks drivers and other software across kernel updates that is the problem. It makes the OEMs do a lot more work for Android updates than for Windows Mobile updates, for example.

Windows Mobile updates were AWOL back then because lots of people didn't care. Trust me, if it was as big as Android is today and Microsoft was doing a 6 month update cycle on it, people would have already graduated to perpetual *****ing about the lack of updates.

They're already doing it with WP7.

Only an idiot would prefer Microsoft drivers to drivers from the component manufacturer.

That's not meant to denegrate you, but the statement is just laughable.

Microsoft only creates generic drivers. Most of the drivers in the Windows Driver Database comes from the Component Manufacturers, not Microsoft. Microsoft doesn't have the resources to test every component that can be put in a Windows System and write drivers for it. Apple doesn't either, and there are tons of components that aren't Apple-branded that are compatible with OS/X with OS/X drivers from the component/device manufacturers.

Maybe Microsoft should have told Apple to write their own Zune Drivers so that WP7 users could use iTunes to Sync their Zune HDs and WP7 devices, then?

See what I did there?

IRT performance regression. There's a difference between running a graphics card with a generic driver and running a high end graphics card with a generic Vesa Driver that can barely get above SXGA resolution with bad 2D accelleration, and probably no decent 3D acceleration to speak of. Printer drivers that leave the Printer Crippled and the Copy/Fax functionality of an All-In-On device inop. Screen Drivers that don't support the touchscreen functionality of your All-In-One. Generic WiFi drivers that leave your networking crippled.

Then when you look at smartphones and realize that one bad driver can literally half your battery life or make your phone barely usable... It's just a dumb idea to outsource driver development to lolMicrosoft or lolGoogle or lolApple when they really don't have as good a grasp on how the device/component functions. All device/component manufacturers have software development teams. It's disingenuous to count them out because their main business is components. They write the drivers for them, just as they should.

If you think a Microsoft developed driver is more stable than an OEM/Component Menufacturer driver then I dunno what to say. May I ask you where you're extrapolating this false information from?