The Windows Cloud Problem

The problem for Microsoft is that while edge does support a wider range of html5 apis, it doesn’t support the full range.

The reason why Google’s chrome has taken the lead in browser share is that it supports the full range of html5 apis, from webrtc to webmidi.

Microsoft may have decided that supporting webaudio is good enough for html5 gaming and there is no need for webmidi support.

There’s a problem with that thinking, if its in the html5 spec its important to implement the api or at least have it on the timeline.

Trying to pare the scope of html5 simply by deciding not to implement parts of it as Microsoft and Apple have done is hampering both the ipad pro and will limit the reach of Microsoft cloud.

While they may push back a bit at Google in education, when it comes to music education its going to be a crippled platform compared to chrome os.

Chromeos has beat up both the ipad and windows pretty badly because its dirt cheap but it supports the full range of html5 apis.

Perhaps in a world where net neutrality gets demolished the paradigm may shift and we may see a rebirth of tablets as machines have extremely limited web access.

That brings in another problem for MS, what happens to a cloud based OS when net neutrality gets nuked?

Perhaps we could hope that MS will put its considerable weight behind the fight to keep the web open and high performance for every application.

The future of chromeos and MS’s new cloud windows depends upon an open and healthy internet ecosystem.

Without it, Balmer could be right after all, that these cloud os’s are just paper weights.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.