4 ms·
I already told you why not. Because anything that gives the Surface an advantage has that antitrust lawsuit smell. > Hyperbole much? Again, no. Any move to gi
by drewcrawford 13y ago
I already told you why not. Because anything that gives the Surface an advantage has that antitrust lawsuit smell.
> Hyperbole much?
Again, no. Any move to give preferential treatment to MS's own hardware is the push the OEMs need to convert their Windows Tablet initiative into an Android Tablet one. Not to mention having potential ripple effects in unrelated businesses lines like spooking HP into doing more Linux servers.
For better or for worse, Microsoft's most valuable asset is its OEM partnerships. It's not as cool a trick as it used to be, but it's the only card they have to play.
- macspoofing 13y ago>I already told you why not. Because anything that gives the Surface an advantage has that antitrust lawsuit smell. Who says it needs to be Surface only? Who says it needs to be limited to Microsoft hardware? If the changes need to be in the driver or hardware layer, all Microsoft needs to do is release specs and then setup a certifying service for OEMs. Something like "Battery Optimized" cert that the partner can then communicate to the end-user. However, I have a feeling that lots of improvements can be done at the OS level to boost battery life before you start thinking about changing your driver model. Bottom line this can be done. Windows tablets can and should be able to match Apple hardware in battery life and I have no clue why you're arguing they can't.
- drewcrawford 13y ago> all Microsoft needs to do is release specs and then setup a certifying service for OEMs So this exists. It's called the Windows Logo Program for Hardware. The reason we are reading this article is that it failed to do the job. What you seem not to be understanding is that in order to "match Apple hardware in battery life" one also has to "match Apple hardware" in the small number of distinct hardware configurations sold per year. Taking that hardware configuration and calling it "a standard" doesn't actually do anything. If your standard is broad enough to support 100 hardware configurations, battery life will be poor. If your standard is narrow enough to only support 2 hardware configurations, OEMs will not build it, because Dell has no way to differentiate itself from Toshiba. To match Apple, Microsoft needs to cut back to maybe 3 models of Windows tablets per year. You can make that into a standard if you like, but no OEM will ever adopt it. They will all (correctly) point out that such a standard is designed for Microsoft's hardware team to implement and to hell with all the third parties.