Unbelievable. Remember back in 2010 when they said they would be using Wayland?
When that announcement came around that 'they weren't using Wayland, but they were using something else' came along, I gave them too much credit, by saying the PR person was likely just mistaking "Wayland" for the reference compositor, "Weston".
But they are making their own display protocol in C++, which some people on the Wayland IRC pointed out that there are lots of stubs in their BZR repo which as ModplanMan points out, the repository was created back in June 2012, and they likely had planning and decision making to do so much earlier. So far the issues they posted in the article and wiki make no sense to the Wayland developers
And it also seems really buggy right now, and they have some issues that give them "weird errors" according to this documentation file: https://bazaar.launchpad.net/~mir-te...ad:/HACKING.md .
If I remember correctly, the Wayland protocol didn't hit 1.0 (AKA the point in time when there will be no more protocol breakage) until October 2012. If they had their doubts or concerns about the Wayland protocol, they had time to bring them up on the Wayland mailing lists.
Now they are going to have to make the toolkits support their own protocol. They mention GTK and QT, but they forgot about EFL, and SDL, and the other projects that have Wayland support already. It would be interesting to see if they actually try to merge the support upstream.
And now that they are creating a new Display Server protocol, to support Ubuntu applications in another distro, there is going to have to be some kind of support for Mir in their Wayland server, on top of xwayland support.
The fragmentation this will bring is going to be TERRIBLE.
What's next, they're going to announce their own KERNEL?!
When that announcement came around that 'they weren't using Wayland, but they were using something else' came along, I gave them too much credit, by saying the PR person was likely just mistaking "Wayland" for the reference compositor, "Weston".
But they are making their own display protocol in C++, which some people on the Wayland IRC pointed out that there are lots of stubs in their BZR repo which as ModplanMan points out, the repository was created back in June 2012, and they likely had planning and decision making to do so much earlier. So far the issues they posted in the article and wiki make no sense to the Wayland developers
And it also seems really buggy right now, and they have some issues that give them "weird errors" according to this documentation file: https://bazaar.launchpad.net/~mir-te...ad:/HACKING.md .
If I remember correctly, the Wayland protocol didn't hit 1.0 (AKA the point in time when there will be no more protocol breakage) until October 2012. If they had their doubts or concerns about the Wayland protocol, they had time to bring them up on the Wayland mailing lists.
Now they are going to have to make the toolkits support their own protocol. They mention GTK and QT, but they forgot about EFL, and SDL, and the other projects that have Wayland support already. It would be interesting to see if they actually try to merge the support upstream.
And now that they are creating a new Display Server protocol, to support Ubuntu applications in another distro, there is going to have to be some kind of support for Mir in their Wayland server, on top of xwayland support.
The fragmentation this will bring is going to be TERRIBLE.
What's next, they're going to announce their own KERNEL?!
Comment