Linked by Thom Holwerda on Fri 16th Aug 2013 16:10 UTC
Talk, Rumors, X Versus Y

In the past two months, Microsoft and Google have been bickering over one central issue: HTML5. The Verge has learned that Google is forcing Microsoft to build its YouTube Windows Phone app in HTML5, despite its own Android and iOS versions using superior native code. Although Microsoft has offered to build ad support along with making other tweaks as Google has requested, a full HTML5 app isn't currently possible on the platform.

The difficult thing here is that Google actually has a very good case; it's their API, their service, their rules. On top of that, YouTube publishers - big and small - need to earn money from advertisements too, and incorrect implementations make that harder. Microsoft's mafia practices regarding patents, extorting companies to pay for Android use even though Microsoft has contributed zero code to Android plays a role too. Lastly, Windows Phone is essentially irrelevant with 3% market share - it's not as if Microsoft ever concerned itself with minority platforms.

Still, all this does is hurt consumers, no matter how few Windows Phone users there are. Just work this out, please, you bunch of children.

Thread beginning with comment 569899
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: The nuclear option
by zsekeres on Sat 17th Aug 2013 10:53 UTC in reply to "The nuclear option"
zsekeres
Member since:
2011-02-11

Ah... FUD

I think there is a reason why BYOD is an issue these days. Employees are more comfortable with the devices they know (and often enough love) at home. Consumer stuff, i.e. basically Android and Apple given the current market shares.

So I guess if the "nuclear option" would be exercised productivity would suffer because employees are forced to get along without their favorite devices. Or how about this:
- An important service goes down on a long weekend.
- Turns out that an engineer is required who is not on call duty. (Yeah, this happens...)
- As the engineer has only his personal iPhone or Nexus phone with him and Exchange is not supposed talk to these evil devices he will enjoy some happy holidays.

(Actually close enough to an incident I experienced...)

Reply Parent Score: 3

RE[2]: The nuclear option
by Nelson on Sat 17th Aug 2013 12:12 in reply to "RE: The nuclear option"
Nelson Member since:
2005-11-29

BYOD is one tidal force, EAS and Office 365, as well as InTune is another one. Microsoft is so absolutely engrained in the enterprise (mainly because EAS is uncontested in what it does, lemurs pathetic alternatives aside) that they have significantly more leverage than Google does here. They'd kill GApps for Business over night.

Reply Parent Score: 3

RE[3]: The nuclear option
by lemur2 on Sat 17th Aug 2013 13:15 in reply to "RE[2]: The nuclear option"
lemur2 Member since:
2007-02-17

Microsoft is so absolutely engrained in the enterprise (drivel redacted) that they have significantly more leverage than Google does here. They'd kill GApps for Business over night.


This is precisely the kind of "Microsoft way or be dammed" attitude that sane businesses should fervently seek to avoid.

Certainly if any IT person expressed such an attitude to me I would be utterly keen to make sure they were not part of my IT staff.

Reply Parent Score: 3

RE[3]: The nuclear option
by JAlexoid on Mon 19th Aug 2013 09:45 in reply to "RE[2]: The nuclear option"
JAlexoid Member since:
2009-05-19

They'd kill GApps for Business over night.

How would that be? Android and iPhone don't need EAS to access GApps and Outlook integration is done using Google's own sync agent.

Reply Parent Score: 2