Linked by Thom Holwerda on Mon 4th Mar 2013 18:26 UTC
Ubuntu, Kubuntu, Xubuntu "Canonical has today publicly confirmed that they are working on a new cross-platform displayer server for Ubuntu. Called 'Mir', the X Window Server replacement is tasked with 'enabling development of the next generation Unity'. Which, in yet another about-turn, is to be rebuilt in Qt/QML." It'll be used for all Ubuntu variants (phone, tablet, desktop), and the first version will be released come May.
Permalink for comment 554184
To read all comments associated with this story, please click here.
RE[2]: Finally
by Nelson on Mon 4th Mar 2013 20:20 UTC in reply to "RE: Finally"
Member since:

There's something seriously wrong if you can't evolve and modify your direction in light of new industry trends and realities.

Remaining steadfast in the face of a sea of change is what made Microsoft miss the boat on mobile.

Microsoft's client side evolution (from a managed POV, native has always been a mess until Win8) has always been about XAML and a GPU accelerated framework.

-> WPF 3, 3.5, 4, and 4.5
-> Silverlight
-> Silverlight 2,3,4,5
-> Silverlight for Embedded
-> SL 2.0 for Symbian
-> Moonlight
-> Silverlight for WP
-> Silverlight for XBox

So we had two divergent technology branches based on the same core technology for the last half a decade. WPF was the result of a botched Vista dev cycle and showed it. Silverlight was slimmed down, almost beautiful in how simple it was, but ultimately a science project (albeit one that got too successful for WinDiv to stomach)

However, despite the differences in API surface, a lot of the architectural design decisions remained persistent:

Dependency Properties
Storyboard time based and keyframe animation
GPU acceleration

Sharing code between SL and WPF was easy, share code from WPF to SL was hard (since WPF is a superset, put simply)

From there we got the convergence of native and all the managed stacks into the Windows Runtime.

This unified not only WPF and Silverlight by bringing SL into the client, but it unified .NET and COM in a much more natural way.

Prior to WinRT, Microsoft released great COM based APIs for Windows (Win7 Taskbar APIs for example) but .NET wrappers came months, sometimes years later.

With WinRT the projections are automatically generated and the ABI is uniform so calling into native code from .NET is much more natural and faster (for coarse grained ops)

I think over the past 7 or so years Microsoft's vision has remained consistent, but the means to get there has changed slightly. Silverlight went from an RIA plugin , to an OOB solution, to being reborn as the XAML platform in WinRT (gross simplification).

Thankfully, WinRT has restored sanity to native code. I can write super fast native code, interop with my C# app, and not have to see a single IUnknown or AddRef (save for DirectX). Its great.

Going forward I expect almost every new API out of MS to use WinRT.

Reply Parent Score: 5