Steam installieren
Anmelden
|
Sprache
简体中文 (Vereinfachtes Chinesisch)
繁體中文 (Traditionelles Chinesisch)
日本語 (Japanisch)
한국어 (Koreanisch)
ไทย (Thai)
Български (Bulgarisch)
Čeština (Tschechisch)
Dansk (Dänisch)
English (Englisch)
Español – España (Spanisch – Spanien)
Español – Latinoamérica (Lateinamerikanisches Spanisch)
Ελληνικά (Griechisch)
Français (Französisch)
Italiano (Italienisch)
Bahasa Indonesia (Indonesisch)
Magyar (Ungarisch)
Nederlands (Niederländisch)
Norsk (Norwegisch)
Polski (Polnisch)
Português – Portugal (Portugiesisch – Portugal)
Português – Brasil (Portugiesisch – Brasilien)
Română (Rumänisch)
Русский (Russisch)
Suomi (Finnisch)
Svenska (Schwedisch)
Türkçe (Türkisch)
Tiếng Việt (Vietnamesisch)
Українська (Ukrainisch)
Ein Übersetzungsproblem melden
Diskussionsregeln
Diesen Beitrag melden
It's nothing more than "Canonical vs The rest of the Linux world".
Considering the reasons why they made their own display server, it's no wonder why the there is no one standing behind them.
what debate Mir is a fish out of water
Go Intel The hero we deserve!
Why should they mantain anything just for Ubuntu.
Thats not how Linux works.
And why cant the dev working on mir work on Weyland ?
I would like Canonical to explain that to us.
But I am not holding my breath.
yes, it does if you as a company invest half of the time and the money you are going to invest in your own project, but of course then you cannot license it as you like. (Read the license of mir to understand it)
It doesn't usually involve altering your fork underground for months, before announcing it to the world as a new project while slinging insults at the community who developed the original code-base. If Mir was just a fork I doubt anyone would have an issue with it.
As it is no one seems to have an issue with Mir itself. Canonical's arrogant behaviour and development path is the problem.
Problem is investing in doesn't give you control over the direction of the project. This is really where the problem comes from.
Canonical has very specific goals they are trying to achieve with Mir (and Unity) and they didn't feel that Wayland was going in the direction they wanted (as Gnome wasn't).
we currently have 3 very distinct goals in the Linux world right now. Distros focused around the Community, Distros focused around Enterprise users and Distros focused on gaining end user acceptance.
For the most part Canonical is alone in their goal. There are other user friendly distros, however the goal of them is to take the Community and Enterprise tools and make them easier for end users, where Canonical is (somewhat taking from apple) wanting to make something the end user wants.
The former two camps are not generally interested in the average user as most of us who are here can fix our own problems and don't mind working through issues. Problem is we are unlikely to get the mainstream acceptance we want if we all stay on that path.
Can Canonical keep the delicate balance of doing there own thing and being compatible with what the community is doing? Only time will tell, but I don't think it's time to condemn the project till we actually see how it turns out.
Well all your websites are obviously telling crap. The first native Wayland desktop will be released this month with Gnome 3.10. Native Mir desktop is targeted for 14.10, so over a year away! Jolla Sailfish Phone with Wayland will be shipped this year as opposed to Canonicals failed Ubuntu Phone campaign. Waylands reference compositor Weston worked nicely on mobile with multi touch input over 6 months before Canonical announced Mir. Google "Weston Galaxy Nexus".
There isn't a single technical reson why Canonical decided to develop Mir. It's all about creating an Android like ecosystem totally under control by Canonical.
But you forgot one important part: Canonicals CLA.
Probably the biggest difference between Wayland and Mir is that Mir stands under Canonicals CLA. I cannot understand why someone would support that.
AFAIK, Mir is basically Wayland with server-side decorations, with an Android library that I can't remember the name of right now. This allows them to use Android graphics drivers. It's an oversimplification, but the point is that Wayland is extremely flexible, and can be extended to do everything Canonical needs.
If Canonical had put the man-hours into developing Wayland further, imagine how far it'd be.
Sometimes it's necessary to reinvent the wheel - but it's just senseless to do it twice, when the first reinvention was better!
I think Enlightenment was planning for a March Wayland release - not at all sure though.
Regardless, a split is imminent if Cannonical continue on this path.