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.
Thread beginning with comment 554164
To read all comments associated with this story, please click here.
Finally
by leos on Mon 4th Mar 2013 18:31 UTC
leos
Member since:
2005-09-21

When in doubt, rewrite.
They've finally made the right choice of toolkits, but I can't help but feel they're being way too scattered about this. Just a couple weeks ago they were recomending everyone use Python and GTK to develop their "apps" and now they're pulling that rug out again.
If you know you're going to standardize on Qt, then don't make major announcements based on a completely different environment just weeks before. For a small company, Canonical sure behaves like a massive one where the left arm doesn't know what the right is doing.

Reply Score: 10

RE: Finally
by No it isnt on Mon 4th Mar 2013 18:44 in reply to "Finally"
No it isnt Member since:
2005-11-14

Ubuntu have written a lot of things, but, AFAIK, none of it has been picked up by any other distro. They should stick to what they do best, which is to repackage other people's work, and not try to fork the Linux desktop.

[edit:] Of course, if Ubuntu actually for once make a superior product in shorter time than the competition, then that's a welcome contribution. For some reason, I just don't have any faith in them at all -- but the X.org developers behind Wayland hasn't really shown any reason why I should trust them more.

Edited 2013-03-04 18:55 UTC

Reply Parent Score: 2

RE: Finally
by WorknMan on Mon 4th Mar 2013 19:11 in reply to "Finally"
WorknMan Member since:
2005-11-13

Just a couple weeks ago they were recomending everyone use Python and GTK to develop their "apps" and now they're pulling that rug out again.


Sounds a lot like MS, doesn't it? Seems like every 3-5 years, MS is 'betting the company' on some new technology.

Reply Parent Score: 7

RE[2]: Finally
by Nelson on Mon 4th Mar 2013 20:20 in reply to "RE: Finally"
Nelson Member since:
2005-11-29

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 -> WPF
-> 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:

XAML
Dependency Properties
Storyboard time based and keyframe animation
GPU acceleration
Databinding

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

RE: Finally
by Soulbender on Tue 5th Mar 2013 04:16 in reply to "Finally"
Soulbender Member since:
2005-08-18

If you know you're going to standardize on Qt, then don't make major announcements based on a completely different environment just weeks before


Better to change direction now before everyone's on the Python/GTK train.

Reply Parent Score: 5

RE[2]: Finally
by TechGeek on Tue 5th Mar 2013 05:28 in reply to "RE: Finally"
TechGeek Member since:
2006-01-14

"If you know you're going to standardize on Qt, then don't make major announcements based on a completely different environment just weeks before


Better to change direction now before everyone's on the Python/GTK train.
"


If I remember, Gnome settled on javascript, not python. I wonder if this is the reason for the change now. Maybe Canonical has lost faith in the Gnome community. They would not be the first to wonder where the heck Gnome is going. Personally I don't see how you can base all your desktop apps on javascript, unless they are all web apps, but I am not really a dev.

Reply Parent Score: 2