The Motley Fool Discussion Boards
Stocks M / Microsoft Corp.
|Subject: Re: Paul Otellini: Windows 8 'Not Ready'||Date: 9/27/2012 8:35 AM|
|Author: Philipo||Number: 155911 of 157164|
"Problem is no matter how much time you give developers its never enough."
That's too dismissive of the REAL problem. And why is that an acceptable excuse for a MS OS that's been in the making for years but not other products that have as high or less exposure? Who's steering this ship - the developers or management?! Who in this business doesn't know that drivers are the 1st thing a tester or a user cares about because their hardware is worthless without that support? Is just as MS's own executives that threw hissyfits when their printers won't work. It seems selective short term memory strikes again.
The real problem is MS keeps changing driver models every 2 OS versions and doesn't plan accordingly for the backlash. Don't blame the 3rd party developers for that or the lack of a decent early SDK or even these days for the lack of something like a driver emulation-translation layer (many of the drivers that lag or get orphaned are for lower performance devices yet valued ones - a form of VM where you didn't have to buy an old OS license is well withing MS's powers).
And if you want to be taken seriously don't infer it's about the developers that always just want more time - they do what they're told by managers and often are given cross purposes & impossible schedules. Managers steer the ship and sight the goals - developers pull & feather their oars at predicitable pace.
"Everyone seems to forget the massive driver issues that XP had, far more than Vista."
Wrong - XP didn't have slight or massive driver problems (specifically) because drivers from W2K/NT5.0 worked fine with it (still do). You're confusing driver problems with other problems XP DID have. Vista on the other hand was a new driver model and was an admitted disaster as evident from the emails from MS executives complaining that even they were effected & frustrate