3 ms·

> The only good thing Mir brought to the world was competition Not true at all. Various years before Mir started, Canonical publicly said the future was Waylan

by bkor 10y ago

> The only good thing Mir brought to the world was competition Not true at all. Various years before Mir started, Canonical publicly said the future was Wayland. Canonical promised to do some work on Wayland. They started Mir, didn't do that work, then 6-9 months later announced Mir. They delayed that work for 6-9 months due to keeping Mir a secret. There's NO speedup due to this. It caused delays. Wayland was already at 1.0 by the time Mir was announced. However, that 1.0 was for basic things. After this it needed desktop environment standards. That's what the various desktop environments needed to work on. Initially that was GNOME, Enlightenment and KDE. Due to those agreements you could finally actually see the results of many years of work. Practically though, things could've been faster with Canonical also joining in (making/agreeing/discussing standards, etc).

eptcyka 10y ago
That is the point, they stated publicly that Wayland was the future, which was a dick move. However, while wayland was at 1.0 by the time they announced Mir, Gnome and KDE were far from using Wayland in production. Even today, I do not use Wayland on Gnome because it doesn't support hot reloading of the compositor, Intel's work on bringing a native Wayland frontend to Chromium is MIA. But I guess my contemporary gripes with Wayland have nothing to do with Mir and everything to do with the fact that Wayland was just a protocol that a number of independent parties had to agree upon and implement correctly. Even today, Nvidia doesn't want to play ball when it comes to Wayland compositors interfacing with their proprietary drivers. Whilst commit frequency does not display this, I still believe that developing Wayland was taken more seriously after Mir was announced. This is however my suboptimal opinion, and I am willing to concede that I am wrong and discuss the matter further.

by bkor 10y ago

eptcyka 10y ago

That is the point, they stated publicly that Wayland was the future, which was a dick move. However, while wayland was at 1.0 by the time they announced Mir, Gnome and KDE were far from using Wayland in production. Even today, I do not use Wayland on Gnome because it doesn't support hot reloading of the compositor, Intel's work on bringing a native Wayland frontend to Chromium is MIA. But I guess my contemporary gripes with Wayland have nothing to do with Mir and everything to do with the fact that Wayland was just a protocol that a number of independent parties had to agree upon and implement correctly. Even today, Nvidia doesn't want to play ball when it comes to Wayland compositors interfacing with their proprietary drivers. Whilst commit frequency does not display this, I still believe that developing Wayland was taken more seriously after Mir was announced. This is however my suboptimal opinion, and I am willing to concede that I am wrong and discuss the matter further.