I summed up my thoughts at the time here, in the end C removed the lies, but I'll still bet we'll see them repeated by fanbois across the Internet for years, and developer time will have to be spent correcting them.
I'll update the blog post to mention that they have removed the original source of the technical untruths.
The thing is if you think this is was a purely technical decision at Canonical's end you are already sucked into their event horizon, sometimes you have to realise technical isn't the game that you are being played in and address it as such.
Posted Mar 6, 2013 21:32 UTC (Wed) by man_ls (subscriber, #15091)
[Link]
Of course I don't think it's a purely technical decision from Canonical. Also, I don't necessarily think it is a good decision, either for them or for Linux as a whole. But I do think that many good things can come out of it: new ideas, new code, encouragement for Wayland devs to finish their job.
As to the downside, there may be bad consequences, but I don't see how we may end up with three (or four!) different, incompatible display servers. Either they will be compatible somehow or only one will survive. Hey, even GNOME and KDE have agreed to a lot of standards, making our life easier.
Thanks for making my argument
Posted Mar 6, 2013 23:36 UTC (Wed) by HelloWorld (guest, #56129)
[Link]
> But I do think that many good things can come out of it: new ideas, new code, encouragement for Wayland devs to finish their job.
Name one reason why new ideas and code can't be created by extending Wayland.
> As to the downside, there may be bad consequences, but I don't see how we may end up with three (or four!) different, incompatible display servers. Either they will be compatible somehow or only one will survive. Hey, even GNOME and KDE have agreed to a lot of standards, making our life easier.
Yeah right. Gtk applications look alien on Qt-based Desktops to this very day. If anything, the Gnome/KDE history is a cautionary tale.