OSNews

Here is what I predict, and I did call both Vista and Win 8 right on the nose.

Within 3 years all of the OEMs will be selling ChromeBooks and ChromeTops instead of Windows PCs (because they frankly have NO choice, not only is MSFT sticking it to them with OEM pricing but also stabbing them in the back by announcing they are gonna build their own desktops, laptops, and phones to go with the tablets so every dime they give MSFT is a dime to a company that wants them out of business) and Google will own the low end while Apple will keep the high but will see their market shrink as Android devices become more powerful and cheaper. Cook has already seen this trend, hence the iPad Mini, but when you will soon be able to buy multicore Android tablets for 4100 it will be hard to get more than the Apple faithful to buy your next $500+ products.

The only thing that worries me about this is it is increasingly looking like Google is gonna keep ChromeOS locked down and OEM only, looking at the new ChromeBooks you can't even run Linux on them without 3 pages of CLI and a lot of finger crossing, so we may end up replacing one company that wants everyone locked down into black boxes with another and for those of us that like to build our own hardware things look quite bleak indeed.

It is increasingly likely that computers will become the new consoles, locked down and disposed of when the companies no longer support them, just as an old GameCube is worthless for anything but some legacy games. Its a real shame as we are getting all this crazy powerful hardware that will end up going to the dump even when it could be used, simply because you'll have no access to the hardware at all.

I think that you mean "you will soon be able to buy multicore Android tablets for $100".

Yeah sorry about that, I really need to take the number 4 key off my old clacky and clean it as its hit or miss, especially when I'm typing quickly.

But my point still stands, just as IBM started the PC market by using a little OS later known as "MS-DOS" because they couldn't get CPM so too is the OEMs gonna have no choice but to switch as every dime they give MSFT is money that will be used to try to put them out of business. Just look up the "Windows Blue" memo by Ballmer's team, I'm sure every OEM has read it by now, where it states flat footed that "The future of Windows is MSFT hardware running MSFT software and sold in MSFT stores" thus making it clear they consider the OEMs to be history as far as MSFT is concerned.

They will gouge the OEMs for every penny they can, thus not only taking money from a rival but also making it harder and harder for them to sell a Windows machine and make a profit, so their only choice will be to switch to another OS or close the doors, simple as that. While I'm sure the OEMs hope that Ballmer gets fired and somebody who understands the Windows ecosystem brought in you can't base your business on hopes so I have NO doubt they are all setting up meetings with Google as we speak.

Ironic that the FOSS zealots dreamed for years that MSFT would just dry up and blow away, but who would have thought the death of MSFT would come not from a competitor but from a truly pathetic CEO killing the company trying to raise the stock price.

I just tried to correct a number you gave. I didn't said that your point didn't stood; greedy managers lead those companies to abuse, and, like you say: people will react buying other kind of computers... or "computers will become the new consoles, locked down and disposed of when the companies no longer support them".

I'd really like to hear more about this.

The first barrier is that there is no equivalent industry-wide "DAV" for e-mail. I'll actually ignore that, though, as at least in theory one could develop.

For mobile sync, the primary focus will be on efficiency and prompt change notification. Dedicated sync protocols can do this fairly well, and aggregate all the data types (email, calendar, contacts, tasks) into a single point, delivering changes to them in near real-time and minimizing the number of open connections required on the phone (important for battery life). The integration is key, because some of these are more closely related than you'd think. I get an e-mail invitation, which needs added to my calendar--and my free/busy index updates so other people can see I'm booked--and then I do a search in my company contact's directory to add another attendee.

That tight integration is missing in the DAVs, as is any standardized method of "pushing" changes.

Another big one is the fact that now I have all this important mail, calendar, and contact data on my phone, what if I lose it? What if my company wants to make sure I use a PIN? Sync protocols usually include extra commands to provision the phone according to company policies for encryption and passwords, allow remote wipe, &c.

DAV is great as an API, but to turn it into a sync protocol, you really need some kind of shim in between that trims it all down, aggregates the data sources, simplifies change notification, and provides just the subset of functionality needed on mobile devices, while adding in specific new capabilities like remote wipe. When people feel like getting super fancy, that can also add mobile enhancements like sending only the new text in a reply or a forward, pulling in the original text on-the-fly, and other such niceties.

But by the time you've done all that, it no longer looks like plain-vanilla DAV.

Edited 2013-01-03 22:14 UTC

Prompt change notification is only relevant to messaging. Calendar, contacts and tasks are not time critical, or are already triggered by other messages.
Also, the number of connections is not as important as the amount of data that needs to be transferred. CDMA networks spend energy per bytes transferred, TDMA per time connected.(Thus standby time for TDMA is lower than CDMA)

What DAV and IMAP are not are sync protocols.

Not knowing the limitations and differences of design goals of *DAV versus EAS, I would like to hear more, as well.

They were broken because YouTube changed its API in various ways. That's life. APIs change. Third party developers adapt. Every company known to man does this, and there's no evidence WHATSOEVER that this was done on purpose just to break everything.

They are also not "routinely broken". That's a clear and utter lie. I've been using YouTube+ for god knows how long, and this was the FIRST time this happened - and it was fixed quickly.

MetroTube and YouTube+ (and various others) are evidence that Microsoft is making excuses for its own failing to provide a good YouTube application.

MetroTube and YouTube+ break because they use non-documented APIs, the public facing YouTube API has hardly changed.

Why does MetroTube need to use these APIs?

Wait for it.


Because YouTube doesn't offer up an API. It's also interesting that only third party YouTube apps which are forced to use these APIs break, and not officially sanctioned YouTube apps.

The fact that you make excuses for this is ridiculous.

They break because the API changes. Documented APIs change too. Third parties adapt. That's life as an ISV. Ask the SAMBA guys. Ask OpenOffice. Ask anybody who has ever had to tap into someone else's APIs, specifications, or standards.

You have offered up zero evidence that this is all a big conspiracy to harm consumers using Windows Phone, as you claim. Until you do, you're just rambling nonsense.

The public facing YouTube API changes rarely. But, if it changes, that's great. Because it's documented.

When YouTube changes their private API, in an effort to subvert MetroTube and other third party apps, it becomes a bigger deal because time must be spent figuring out a work around, resubmitting to the Windows Store, and hoping it doesn't break again.

You're suggesting Microsoft use undocumented APIs and submit it out to consumers on the hopes that Google doesn't decide to do something about the blatant violation of their terms of use. Perhaps Google can willy nilly ignore the legal ramifications of what they do with others property, but Microsoft can't.

Why is it so difficult for you to get behind Google opening up their YouTube API? Why is it so hard for you to point the finger at Google?

Proof buddy! You have none. If you do, please show it. Otherwise, this conspiracy of yours is bullshit.



It would be great if they did - but the fact of the matter is, is that it doesn't seem to matter. Closed or not, there are fantastic third party YouTube applications, and for the first time in eons, we saw breakage a few weeks ago that lasted a whole day (wow!). It'd be great if they opened it - it just doesn't seem to matter.

So providing access to the API for iOS and Android clients but refusing to grant Microsoft permission to use said API, and refusing to grand MetroTube permission to use the API isn't a direct attack on third party YouTube apps?

I really struggle to understand your thought process sometimes.

A couple of things. Firstly, I don't understand what _you_ don't understand about the work "private" in "private API."

Second, I don't understand why, exactly, it is you think that they are in any way, shape or form obligated to provide the same level of access to 3rd parties to begin with...

Those iOS and Android apps? They were developed _by Google_ last I checked. Could it be, just maybe, that they don't see the _value_ in developing a Windows Phone version because it's just not a large enough market and viewed as a waste of time?

And maybe, just maybe, part of the reason that they don't have a fully featured public API is that they are still changing it and don't want to be tied to an API interface that would be sub-optimal? The fact that the private interface changes and breaks things is a bit of a hint...

They've been doing an awful lot with YouTube lately that seems to be in an effort to bring it in line with the rest of Google's product offerings and this may be part of that.

OR

Perhaps they don't have a "fully featured" public API because, well, they just don't want to.

Which brings us full circle back to using private APIs to build one. Well thats cool. Go ahead. But understand that if you use undocumented, private APIs to do anything they _can and will_ break. It's not necessarily trying to actively subvert 3rd party clients. It's a developer changing an internal API. Private APIs are subject to change at _any time_ without notice because they are PRIVATE. That's what PRIVATE API means.

Get. Over. It. There is not conspiracy. Some just did the equivalent of changing a function signature or move a class around.

There is no conspiracy. That's just how software development works.

That's like saying that it doesn't matter that Windows is closed source because it can be pirated.

I wondered when Mr. Cognitive Dissonance would show up. As always, I can rely on you to disregard 7 years of posting history chock full of love AND criticism for each AND every company, just to maintain your world view.

I've been for and against everything, buddy. Nobody takes nonsense like that seriously anymore. I've advised people to switch to DuckDuckGo. I point and laugh at Google+. I regularly dump on Chrome for Android. I have posted countless articles on Google's utter failure in the Android update situation. I have condemned Google for its actions regarding the handling of adult content in image search. I have condemned Google's actions regarding SkyHook, going even so far as to interview the CEO of SkyHook himself. And much more.

But sure, I love Google. Whatever you say. I don't think "love" means what you think it means.

Edited 2013-01-03 11:23 UTC

So you have a love-hate relationship then.

What does that even mean?

What open source thing has Google participated in that devalued other companies' business models?

And yes, Google is not going to open up their algorithms, but when have they actually sued a competitor over their search algorithms? Even when Bing was alleged to have copied Google's results, they did nothing than write a strongly worded blog posting.

The fact that Google is actively making sure it's hard to download copyrighted material from YouTube is evidence to the contrary - protecting IP that does not belong to them.(FYI: YouTube videos don't belong to Google)

OOXML and the network protocols SAMBA uses are open and documented standards/protocols.

YouTube is not. You can't find documentation to make a fully featured YouTube client. I don't think you understand this.

And yet, they exist. Many of them. Often better than Google's own offerings. It would be great to have it open, but from a practical standpoint, it doesn't seem to matter.

The point is that exist in spite of Google's efforts, and they constantly need reengineering to work again. It's far from a pleasant experience.

MetroTube has broken 2-3 times in the past year, and then earlier in 2011 for over a month. To say this is good enough, and then dismiss Microsoft's claims as petty is unfair.

But okay, I get it, you did your little OSNews hit job of the week. Good job.

Thom, you're desperately wrong on this! MetroTube is a hack which uses undocumented APIs to get access to youtube's content.

iOS and Android are given unrestricted access to the public APIs, but Windows Phone is blocked.

Microsoft have a 'MetroTube' available, but the reason they can't release it is because they're obviously under a lot more scrutiny and can't get away with what indie devs are doing.

That is incorrect. YouTube apps on Android and iOS get unrestricted access because they are made by Google and are 100% proprietary.

YouTube API on Android and iOS is no different from API on WP8.

Huh?

https://developers.google.com/youtube/

Edited 2013-01-03 05:41 UTC

Have you actually tried to use the API? Are you stupid? Is this entire article made up? Are the issues that third party Windows Phone and Windows Store apps have imaginary? Are you inebriated?

YouTube offers a SUBSET of APIs available, you CANNOT build a fully functional YouTube client using the public API because it is incomplete and only allows for superficial integration with the service.

If you had bothered to read the documentation (you didn't) or even bothered to try to implement the API (again, you didn't) or even did the slightest amount of due diligence (nope again) you'd know this is true.

This is what is truly infuriating, you're so interested in a fucking gotcha that you don't even take the time to do basic research.

You made a claim, and I simply pointed out a link to the documentation for the youtube APIs. If you have nothing to add to the conversation so be it, no need for silly strawmen about what I may or may not have done.

Sorry to butt into the convo here, but:
Documentation to create a fully featured YouTube client:
- http://www.w3.org/TR/2012/CR-html5-20121217/
- http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-2...
- http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devne...

There's some other docs those ones depend on but that's pretty but the core of it right there.

Of course, most computing devices have at least a partial implementation already.

;)

thom you are loosing credibility i'm surprised

i'm sure you can't see the bigger commercial picture (not conspiracy) being played out

Furthermore, Microsoft has stated they are ready to release a YouTube app, and is just waiting on consent from Google to do so, since it is part of the non-public API.

Google refuses to do so. Microsoft has stated that the YouTube team themselves would like this to happen, but higher ups at Google prevent this from happening.

Seriously, not having YouTube is a serious chink in Windows Phone's armor, and I don't think Microsoft would lie about honestly wanting a YouTube app on the platform but being blocked by Google. They're not the ones with the leverage here.

MetroTube and YouTube+ have to spoof their requests to make them seem like they're coming from supported platforms. Its a constant cat and mouse game.

Maybe they should stop with their dirt flinging campaigns and FUD spreading. Or maybe they should come stop bashing Google, who they obviously need, and come up with a good offer.

I'm wondering : how MANY times the MSN APIs and protocol slightly shifted and rendered third parties' client non functioning ?

"Hello!!?? Hello!?? ANYBODY HOME!??? Think McBallmer Think?!"

Kochise

Edited 2013-01-03 06:44 UTC

I agree with you. It is wrong of Microsoft.

See what I did there? I acknowledged that yes, it is possible to hold a consistent view point and not be hypocritical.

Of course, because we're gentlemen. If Google is really preventing Microsoft from providing a correct YouTube exprience to WP users, that's not great of them and against Google's "Don't be evil" moto.

However, while the DAV subject refers to "OPEN" protocols, H264 is not. Let's start by sorting out this issue first, or knock's the top of Ballmer's head for not implementing the "OPEN" WebM standart into their Windows products in the first place.

That would sure ease creating streaming clients over YouTube's content.

Kochise

Of course, you're right. But with Microsoft having been evil jackasses for well over a decade, it's kind of hard for me to shed a tear for them. It's like watching a bully finally getting his ass beat.

What can I say? karma is a bitch And Google is going to get theirs one day as well, especially if they continue their path to the dark side.

I hear you 100% on the karma bit, but there are ways to hurt Microsoft without hurting end users.

Google has now purposely crippled their Email offerings and locked out consumers from one of their most popular services, all over a petty pissing contest with Microsoft.

Well, Google really have no obligation to support Microsoft's protocols and it's none of Microsoft's business what Google does.
It might be smart of them to do it but that's a different matter. If users really need this feature it will either a) be re-introduced or b) they'll get a different phone.
What, you think Microsoft cares about how this affect users? No, they care about how it affects the company.

Let's swap roles "Microsoft really have no obligation to support Google's protocols" .

Except I think in these very comments you lambast Microsoft for doing just that.

Pot, Kettle.

Say what? For doing just what? Not supporting Google's protocols? Uh....
I said that Microsoft is still anti-competitive and monopolistic which isn't at all the same thing as Google not supporting EAS.
I also agreed that Google's isn't exactly a saint either.

However, unlike Microsoft's offerings, Google's services are accessible using free and open standard based protocols/technologies.

Like YouTube. Right? No.

HTML5 no?

This is a little unfair. Google provide a means to access their services (Google Apps/GMAIL/etc) using a publicly documented and (mostly) standardised protocol suite (*DAV+IMAP).

Microsoft also provide a means to access their services (Exchange servers & Outlook.com/hosted exchange) via a publicly documented and entirely unstandardised protocol (EAS/EWS for mobile/desktop - there's also RPC[oHTTP] which is a mess even Microsoft is trying to figure out how to get away from and which I'll ignore)

This is in both cases in addition to the web interfaces of course.

Google should no more be expected to provide, for free (to users), EAS and EWS access to their services, than Microsoft should be expected to provide, for free (to users), *DAV+(decent)IMAP support via Outlook.com & Exchange based systems. (Exchange backed IMAP kinda sucks)

In fact, given the open, unencumbered nature of *DAV+IMAP, there should in fact be more reason to expect MS to adopt these protocols in their services than for Google to adopt EWS/EAS.

(Yes I know EWS hasn't come up, but as the desktop complement to EAS it makes sense to mention here)

Except that Google doesn't use the DAV suite (not even implemented by default in Android, ffs) or IMAP with Push on Android or on iOS. They use their Gmail app with a proprietary syncing solution.

So what Google is doing is locking a competitor out, saying they should implement standards that they don't even implement (Because they're not ready for prime time, IMAP doesn't have a true push solution), and then some how, they have tons of cheerleaders here.



Google is leading from behind here, they don't implement the standards they advocate. And I think this is where we differ a bit, I think its fair to expect Microsoft to implement IMAP+*DAV if Google is also expected to implement EAS.

In the end the consumer wins when all options are covered. Just ditching EAS is divorcing yourself from the reality that EAS is in many instances the best way to get push email out of Gmail. Its very heavily used on iOS for exactly that reason.

Only push mechanism is proprietary and undocumented, the actual sync is IMAP(with GMail extensions, documented) and CalDAV+CardDAV.


They may not use those standards everywhere, but they do implement them. (Implement != use)

Edited 2013-01-04 13:09 UTC

No. Android does not implement the DAV suite. Sorry. Contact, Calendar, and Push on Android is proprietary.

So basically what Google did was make their own proprietary syncing solution the only one people have at their disposal while simultaneously not releasing such a syncing solution for Windows or Windows Phone.



So it's do as I say, not as I do? Ridiculous.

It's not available for use for non-Google accounts, but the built-in apps use CardDAV and CalDAV as the protocols.

Maybe because they are not adhering to YouTube ToS and use the same hacks as YouTube video downloaders use. And YouTube video downloaders are violating both ToS and copyrights. These are essentially illegal apps.

I agree. I don't think I ever disagreed. My comment was in reply to Thom saying that because these apps do it, it must be feasible for Microsoft to do so as well.

Read for comprehension.

I don't get it. Are you saying you are Microsoft PR guy?

No, that's not what I'm saying at all. You can however figure out what I'm saying by reading my comment.

The EAS support impacts a lot more people than Windows Phone.

Its just semantics.

Poor Microsoft can't release a YouTube App.

Poor Microsoft doesn't have the support for EAS in a third party application.

Poor Microsoft has to defend itself from the mean Google-Monster.

Get over it. Poor Microsoft isn't poor at all. Its just them complaining because they ran the Computer World for so long, they are getting comeuppance and don;t know how to handle it.

Now if the shoe was on the other foot, and Microsoft was locking Google and Android out of Skype, or Skydrive, or Outlook. Or if Microsoft blocked Google access to the Microsoft Store or whatever underhanded tactic you could think of, I guarantee that you, and many others would be up in arms and this post would have 200 comments instead of just 25.

There is such a double standard that it is ridiculous.

Not particularly true, since Google isn't the Pink 8,000# over-weight bald-headed Gorilla in the room.

Plus... Microsoft have such such such history its not even funny. I mean Microsoft has done that as a matter of course. And where was the double standard there when it was happening? There wasn't, because nobody dare try it to Micorosoft as they'd be *DEAD* commercially... and they *DID* change APIs all the time at any whim and still do.

Its more like why cry for Microsoft right now, when its seriously getting its comeuppance.

Obviously you've only been in the computer industry for 6 or so years, since they started the decline brought on by their decades long haughtiness and hubris.

Its not at all a double standard... its a more of "About effing time they got what is coming to them!"

I'll never shed a tear for Microsoft, they don't deserve a single one. Maybe they could drink their own Alligator Tears.

I get it, Microsoft shit in your cornflakes. They did some terrible, anti-competitive things, but what happened then, is not what is happening today.

Forgiving Google today because of the sins of Microsoft in the past is nonsensical and hypocritical.

I understand full well that you think its some sort of poetic justice, understood, but that doesn't mean what Google is doing is right, or justified, nor does it make it okay for you and others to be so dismissive about their behavior.

Remember, Google's priorities just happen to somewhat align with yours today. They may not tomorrow. So be careful what actions you cheer on.

It absolutely is still happening to this day. What with the changes to Windows Phone 7, 7.5 and 8... RT is an abortion they are slamming into peoples throats...

[g]Forgiving Google today because of the sins of Microsoft in the past is nonsensical and hypocritical. [/q]They haven't even began to be anywhere *CLOSE* to anything Microsoft did or *IS* doing.

There is NOTHING to be dismissive about... its Microsoft going about the whole thing the wrong way and doing the public whining thing that they admonished and quashed companies and peoples for... I can say one thing:

Remember Ed Curry!

Go find out about him.

If Google changes tomorrow or even in 5-10 years from now. It won't be to our detriment, except to commoditize things like Apple's Device Cash Cow or Microsoft's Application Cash Cow.

Soon, Microsoft's and Apple's Cash Cows are going to be relegated to razor thing margin, which is where they should be.

Okay. This has ceased to be productive.

Forgiving Google for what?

For allowing only mobile IE to access YouTube? But not giving the convenience they provide for leading platforms?
For making it harder to setup new* devices from a competing company?(The one that chose only to have implemented their own licensed and proprietary protocol)

Forcing Microsoft to implement free and open standards or actually help develop those open standards is in my interest as well.


Do you think that IMAP Push would have been nowhere is EAS was not as widespread? The internet was built on free and open standards, Microsoft was never a positive element on that front.(from their own internet to promoting standards that include patent licensing)

*-Existing devices will not stop working, you know.

It isn't just Windows Phones affected. Anyone who does not want to use the Gmail app, but wants true push, used to use EAS. Specifically on the iPhone, it was THE way to do Gmail push there.

This isn't about open standards, or how much Google likes DAV or IMAP, its about pushing people to use the Gmail App.



Microsoft and Google earn equal marks for their support. Android does not support DAV. Again, Android does not support DAV. Android does not use IMAP for Push.

The same exact situation is true for Windows Phone.



IMAP Push is a misnomer. There is no such thing as IMAP Push.



I am well aware.

Brilliant example!

Actually, Skype's protocol is locked up - ISV's *cannot* build a full featured client around Skype's protocol without the same kind of issues third party YouTube apps face (even more, in fact, due to the nature of the protocol). Additionally, since the Microsoft acquisition of Skype was first announced, there's been a few licensing agreements for the protocol pulled (Skype for Asterisk being the big example)

Also, last I checked, Microsoft's store didn't support clients running Google's Android. Nor should they be forced to.

Likewise Google should not be forced to support clients running on MS's OS. Especially while Google is not the dominant/monopoly Email/Groupware provider, and while MS Phone 8/RT is such a small segment of the market.

I agree that Skype needs to be opened up. I will however give Microsoft a little tiny bit of leeway, the Skype acquisition was relatively recent and who knows the state of that source code. Judging by how terrible the Desktop app was, I wouldn't be surprise if it was an absolute mess.

But again, I agree this is a move they should make. And that's why I think its so unreasonable of people to try to deflect the blame on Google by going after Microsoft.



But Google will soon need to face the reality that to remain relevant on Windows going forward, they need to use the Windows Store.

It would be a completely different story if Microsoft somehow blocked Google from their Store. However when Google does it via their closed API (and not even that, they refuse to even offer NDA'd documentation, the same courtesy they extend other platforms) its somehow alright.



Google isn't the one writing the client. Microsoft has engineered the YouTube client. Much like they do the Facebook one.

Now I don't believe that Microsoft has to open Skype protocol. Neither does Google have to open up YouTube protocol(which would be harder to do, since YouTube is a good source of content licensing nightmare).
These protocols are tied into a service, they are not general purpose protocols.

It would be nice to have that, but it's not essential. Adopting open protocols would be much better.

The service is nearly ubiquitous and not offering an open way to provide an experience (or even offering under NDA a way to access YouTube, as they did to Apple) is wrong.

Wrong when Microsoft does it. Wrong when Apple does it. Wrong when Google does it.

The issue is that others seem to be able to both simultaneously criticize Microsoft for instances in which they have not done it, but deflect criticism from Google.



A protocol becomes open..if you open it up.

And in the process it is the end-user getting screwed over so that google can have its comeuppance

Microsoft could have addressed all of these years ago. They chose not to.

Addressed what years ago? The DAV suite has only been recently fully ratified.

Does Google implement DAV or IMAP Push on Android? No. They use their own proprietary syncing solution.

Then they switch over to IMAP/DAV, and don't even use it on Android, but somehow have the testiciular fortitude to suggest others do so.

MS only has done that becase they finally acnowlaged that they are kinda non-important... oh the pity - noone want to use IE so we have to give up all this 'jarring experience' bullshit... at MS they were probably crying while coding...

I think its past your bed time.

oh dear, personal because argumentation is lacking...

I went and re-read your original comment. Nope, still didn't find any logic in it.

I'm not sure what I'm supposed to reply with. Maybe I should applaud you for firing your synapses and making a comment?

Congrats. We're all proud.

If anyone remembers Steve Yegge's publicized rant, this is a long running problem with the Google culture. It is incompetence, no malice.

Basically, the point of Yegge's rant was that Google can't do platforms. It takes a huge cultural shift and enormous dedication the kind he claims he saw when he worked at Amazon but was lacking in Google. It seems it is still lacking.

Maybe that's because they still are?



Dude, it's in their mission statement. Who are we to doubt that?

Do _any_ of your comments contain substance? Ever?

Yes.

Oh, because I'm like six pages into your comment history and haven't found one yet. But I'll take your word for it and keep looking.

Wow, don't you have better things to do? Like, I dunno, have a life?

Doesn't seem to. He just trolls really hard on this site.

Trolling is a euphemism for "I disagree with what you say" on OSNews.

How dare I point out the double standard, how dare I point out how blatantly wrong Thom was, how dare I mention that Microsoft should implement the CalDAV and CardDAV. What a troll!

Yes, this same troll that likes Ubuntu's Phone OS, develops for iOS, Android, and Windows, and uses Google Hangouts and Google Voice.

This meme that I'm in the tank for Microsoft, or that I'm trolling, merely because I state my opinion on subjects, or because I dare dare, to challenge the echo chamber here, is so completely off base its not even funny.

If you let me go off on what I feel is wrong with Microsoft, it'll be hard to stop me, but they are actual real issues that they need to address. Not tired accusations of Anti competitiveness, vendor lock in, or whatever it is that gets you all so fired up.

What a troll.

Ya, kicking and screaming as they were forced to. MS is still very much anti-competitive. Google is far from perfect but at least the file formats they introduce are open and documented in full with reference implementations and the protocol extensions are documented.

Nobody forced Microsoft to do any of the above. Unless you have any proof? You called me a troll in your other comment but the only one spreading falsehoods here is you.

WHAT?
The whole SAMBA v4 thing was a Lawsuit that forced them to open the stuff up.

Why was it that Microsoft themselves taught their protocol with Samba, was it because they were OPEN with it... no it was because Jeremy and they other chaps made Samba BUG for BUG compatible with the protocol as implemented over the wire by Microsoft and it is *MUCH* cleaner and easier to read... plus if does/did dual/tri modes.

Or how about the Memory Management mess they did with DOS.

Hmmm, how about them buying and deep-sixing whole companies because they were competition... even though *MANY* commercial customers were materially harmed by them flush the bowl... after they took a dump on those companies?

Again, I'm guessing you have *REALLY* little experience in this industry or you have a very bad memory.

And I mentioned none of those. Do I need to rephrase my question?

I specifically mentioned protocols and services Microsoft has themselves implemented on other platforms. Its one thing to be forced to document a protocol and dump it on Samba, it's another thing for them to go ahead and do the leg work themselves.

Look at HyperV code in Linux, Hotmail/Outlook on Android, Skype, ActiveSync, Silverlight, etc.

The point is to show that Microsoft is (albeit slower than I'd like) turning towards a more general direction.

All of this is lost in your blind fury over the past.

Edited 2013-01-03 06:00 UTC

HyperV code for Linux... purchased product they stapled in, badly at that. Look at the friggin code. Its horrible.

HOTMAIL? Purchased oh so many years ago... HUGE HUGE debacles in getting it to run on Windows. They couldn't get it to run right... actually run at all. They ended up having to throw like 20 times the hardware at the backend just to get sames performance levels that was on BSD.

Outlook? Second most Exploited piece of Software integrated with the OS a bit to deeply... (right along with the ActiveX and insertion of Userland into Ring 0)

ActiveSync? Really, trot that POS out. Its a serious HEAVY and very under documented item that changes nearly daily. (No not really daily, but damned nearly)

Silverlight? What is that? I have to use a Silverlight Application. I have *ZERO* Windows machines in either VM nor in baremetal. I've installed the latest "sponsored" Moonlight. I can't use it... it is unfortunate, since my PCI QSA requires me to upload my tests and proofs and evidence to their Sharepoint Portal and its just doesn't work from either Linux nor from OSX. I can slect things to upload, but CANNOT actually upload them the transfers never start or complete. I've watched the conversations with Linux and OSX and yes Windows... and they conversations only succeed with Windows due to an UNDOCUMENTED feature that the client assumes its okay to continue once the IIS webserver send an ack... but not any "continue" the OSX and Linux clients can't assume... due to the way Moonlight and Silverlight for OSX is written.

I can go on and on and on... I just don't think you get why Microsoft doesn't need nor deserve any pity or special consideration.

Tell me, have you ever been crapped on by a friend time and time and time and time and time and time and time again with updates on being crapped on more often than not... do you stop dealing with the person or do you keep eating the crap?

I know one thing, Microsoft falls into the category that I'll use them only where there is NO OTHER CHOICE and it is required for my continued employment... (Hint: its not for me)

So, seriously Nelson, you've never dealt with Microsoft in its true form... which is still just under the current skin. Its like a Volcano that is dormant but deadly at any time it feels like it.

Cheers, I do believe you'll never get why.

This isn't a list of things for you to opine on, it's examples of Microsoft bringing key services which people value to other platforms. A stark change from the past.

You go on these red herrings about Hotmail on Windows vs BSD and some random crap about ActiveSync and Hyper-V, but your personal opinions are none of my concern, and completely besides the point.

You're so anti-Microsoft it's almost clinical, and you'd rather go on these useless rants than have a sensible discussion.

You were the one bringing up those particular things. I'm just showing you your vaulted Microsoft Golden Halo is more Lead with gold paint than anything lofty.

Just because you don;t have any way to combat facts and good points shows me you "scripted returns and talking points" are running out. You don't have any choice on your flow chart to be ale to provide good enough responses.

I really wish you would bring some real arguments to here rather than crying wolf for Microsoft.

It is not my problem you can't be asked to actually bring ante-points to my points.

Skype was before Microsoft and their development was in full swing for other platforms.

Also supporting Skype on competing platforms was actually forced on Microsoft as part of Skype buyout approval.

Silverlight what? Do they make one for OSX?
Do please look at Hotmail/Outlook on Android, it's a hack.

Yes. That was the whole point.



Again, as I think you also fail to understand, this isn't a list for you to give your opinion on, it is a list of cross platform commitments they have made.

Your comments on quality (which I happen to disagree with, using Hotmail/Outlook on Android, and it has a full implementation of ActiveSync) are your own opinion and not to be misconstrued as fact.

Quality shows their commitment and focus.
Contrast it to Skype app that was in development prior to Microsoft's acquisition.(Which actually looks and works well)

Your "commitments" is also an opinion, that sidesteps the fact that Microsoft is not a major player and has to be on popular platforms to keep it's users. People will not switch to WP8 just because Hotmail/Outlook doesn't work on Android.

There are more official abuses listed by

Microsoft was forced by market conditions. Google makes more apps on competing platforms then Microsoft. Google Maps app on iOS is better then on Android. I'm pretty sure that there is a Google Search app on WP8, as there is one on W8.

Google has started with open protocols(and still do support open and proprietary protocols), while Microsoft is reacting to the fact that they have to implement them to stay relevant.

I think that's just a side effect of a development cycles. From time to time Microsoft's SkyDrive apps are better than iOS, but as the development cycle turns, the improvements come to Windows Phone and Android apps as well.

The Google Search app on WP8 is useless while the W8 app is superb. Google has at least shown that when pressed, it can make a beautiful app for Windows 8, which is what is even more frustrating for end users.



I love how you say "Stay relevant" as if EAS wasn't pretty much de-facto and Microsoft wasn't reaping in serious bank off of it.

Please see my original comment. I did not single out EAS there. The fact Microsoft isn't implementing CalDAV/CardDAV in Exchange would indicate that EAS isn't the area where they have to do something to stay relevant.(And I know that pretty well) Though Google's move with GMail might force them to

As an example - Microsoft moved away from Silverlight(it's not their focus anymore) to HTML5. That is due to market conditions, where they cannot dictate the majority of the market.

They'll get acquired by either Google, Microsoft, or IBM.

MetroTube guys pulled it because Hiding/Unhiding in the Store is an instant process. They wanted to shield themselves as much as possible from the influx of new users and bad ratings/reviews. Windows Phone Store is cutthroat when it comes to reviews. Either it works perfectly or you're 1 starred into irrelevancy.

Maybe... I'm just going by what they told their users - which was that Google did not offer supported APIs for their intended feature set.

iirc, they do it every time Google changes something. Its unfortunate.

I think the biggest takeaway from this story are the dangers of closed data. Especially if you're a big service. Your data should be open to all clients, and all devices to use.

Is it me or is that news article from over a year ago? (Dec 22nd, 2011, discussing a takedown on Jan 1st, 2012, and we are in 2013 ..)

It is an old article, but there was a recent MetroTube outage as well because of YouTube API changes. This one was maybe a week or two ago.

Eck... The year on that article didn't register properly when I read it. I always get mixed up the first few days of a new year. I was thinking it was recent (i.e. 2012)

Regardless, it still supports my argument more or less. A year ago the developer was making the same complaints that Microsoft is making now. Nothing has really changed in the last year, they are still dealing with API breakages as they come. Microsoft can't afford to operate like that - they need guarantees or at least private channel communications about upcoming changes with some lead time.

ActiveSync is one of their most successful things, ever. Seriously.

Until something can be as data and battery efficient while providing true push email then EAS is here to stay.

That doesn't mean Microsoft can't interoperate better and implement the DAV suite and IMAP into Outlook.com and Windows 8 Mail (WP7/8 Mail supports IMAP already).

To me this is the most pragmatic view. Plus, anyone who really wants to can take an ActiveSync license and implement it.

Haha, yeah, anti-competitive behavior is awesome now that the corporate giant of our choice is doing it. Suck it corporate giant we dislike!

In some fantasy land of yours, no one takes a royalty bearing license for anything, ever.

Except that's not how the world actually works. People license things all the time.

licensing can hit bottom line profitability. MS has made no friends with google with their patent extortion fees against android vendors. fair is fair here.

Do you know how much the licensing fees cost Google? I'm not sure you do, so I don't think you're qualified to talk on any potential impact to their bottom line.

If you think a company as large as Google doesn't get major volume discounts you're out of your mind.

So? That doesn't mean you can come whining when someone opts for the royalty-free technology rather than your proprietary stuff.

I think its perfectly acceptable to complain when they disenfranchise a large amount of users and remove functionality with no replacement.

There is no replacement for the functionality EAS brought to the table, there is no evidence this was financially destroying Google, and there is no excuse for doing this with two months notice.

The way some of you contort yourselves to defend this is amusing.