There has been some Twitter chatter about the closure of silverlight.net, Microsoft’s official site for its lightweight .NET client platform. multimedia player and browser plug-in.
I am not sure when it happened, but it is true. Silverlight.net now redirects to a page on MSDN. Some but not all of the content has been migrated to MSDN, but Microsoft has not bothered to redirect the URLs, so most of the links out there to resources and discussions on Silverlight will dump you to the aforementioned generic page.
One of the things this demonstrates is how short-sighted it is to create these mini-sites with their own top-level domain. It illustrates how fractured Microsoft is, with individual teams doing their own thing regardless. Microsoft has dozens of these sites, such as windowsazure.com, windowsphone.com, asp.net, and so on; there is little consistency of style, and when someone decides to fold one of these back to the main site, all the links die.
What about Silverlight though? It was always going to be a struggle against Flash, but Silverlight was a great technical achievement and I see it as client-side .NET done right, lightweight, secure, and powerful. It is easy to find flaws. Microsoft should have retained the cross-platform vision it started with; it should have worked wholeheartedly with the Mono team for Linux-based platforms; it should have retained parity between Windows and Mac; it should never have compromised Silverlight with the COM support that arrived in Silverlight 4.
The reasons for the absence of Silverlight in the Windows Runtime on Windows 8, and in both Metro and desktop environments in Windows RT, are likely political. The ability to run Silverlight apps on Surface RT would enhance the platform, and if COM support were removed, without compromising security.
XAML and .NET in the Windows Runtime is akin to Silverlight, but with enough differences to make porting difficult. There is an argument that supporting Silverlight there would confuse matters, though since Silverlight is still the development platform for Windows Phone 8 it is already confusing. Silverlight is a mature platform and if Microsoft had supported it in the Windows Runtime, we would have had a better set of apps at launch as well as more developer engagement.
I posted that Microsoft’s Silverlight dream is over in October 2010, during Microsoft’s final Professional Developers Conference, which is when the end of Silverlight became obvious. It lives on in Windows Phone, but I would guess that Windows Phone 8.5 or 9.0 will deprecate Silverlight in favour of the Windows Runtime. A shame, though of course it will be supported on the x86 Windows desktop and in x86 Internet Explorer for years to come.
3. Because Chrome OS and Android will merge
As early as 2009, Sergey Brin predicted that Android and Chrome OS
would likely draw closer to each other and then merge. The Chrome
browser for Android is hinting that this is getting closer to reality,
as are various bits of information emerging about Android 5, most of
which point to at least the beginnings of unification.
Android is already dominant in mobile devices
and runs on everything from televisions to refrigerators to tablets.
Chrome has the largest browser marketshare now. When Chrome, Chrome OS,
and Android all start looking very much like each other and all dominate
their respective markets, it’s not a big stretch to start calling
Chrome OS ubiquitous.
4. It’s Google
If Google has proved anything, it’s that they have enough money to keep hammering away at a market until they own it. They proved it with Android on mobile phones. They proved it with their Chrome browser. They proved it with search and related ads. They’ve had their share of missteps and projects like Google+ remain out with the jury. However, if the project is ultimately about growing their core business (namely advertising) and getting ads in front of more people, they’re absolutely dogged. And while their war chest isn’t quite up to Apple’s standards, they can win wars of attrition with just about anyone. Besides, what would you rather see on that connected television? A familiar web browser with snappy app interfaces and a cool Web Store or some kludgy Java interface that doesn’t look a thing like what you use on your desktop, laptop, mobile phone, or tablet to access content?5. Because the web will be all you need
This is already true for most users. In developing countries, the
only personal computing device that many people own is a simple mobile
phone with basic web access. Elsewhere, cloud-based applications
continue to displace desktop applications and increasing numbers of
users spend their days staring at a web browser instead of any
particular application. Microsoft’s Office 365 acknowledges the need for
at least a hybrid approach to the cloud and most of the interesting
software we read about now comes in the form of cloud-based web
applications or mobile apps.
Even Adobe, the last reason I bother using a full-blown PC, started
shipping Muse (a rich WYSIWYG web development platform) this month and,
while not a web application itself, leverages the Air runtime
environment to be small, light, and fast.
The next version of Bethesda Software’s massively popular and
visually stunning Elder Scrolls series? An MMORPG. No, it won’t be 100%
browser-based, but without the web, fans would just be sitting in front
of their aging XBOXes. Goodbye game consoles, hello cloud.
This webification movement has taken off in the last 18 months. It
isn’t hard to imagine what the next three years will do to the way we
think about personal computing. So while Chrome OS got off to a slow
start, it’s only a matter of time until Google can take advantage of
this inflection point at which we find ourselves.
