Seriously, I think I might post this thread on reddit, this is just too funny.
Announcement
Collapse
No announcement yet.
Ubuntu Announces Mir, A X.Org/Wayland Replacement
Collapse
X
-
Ok so if Canonical succeeds with this, we could be having:
- X programs, running either on XWayland over a Wayland compositor or Mir (XMir?)
- Wayland programs, running natively on a Wayland compositor or a Wayland shim/compatibility layer on Mir
- Mir programs, running natively on Mir or a Mir shim/compatibility layer on a Wayland compositor
- Backend-agnostic GTK3/Qt5 programs, running natively on Mir or Wayland
So, a huge mess on the desktop - even worse than it is now with just different toolkits.
Basically, on Mir, there will be first-class and second-class citizens - GTK3, Qt5 programs will be running natively while everything else will have to run via a compatibility layer. More problems for developers.
Wayland would run GTK3, Qt5, and Wayland programs natively, and X programs under XWayland, but it would lack the Android drivers support (unless someone ports them to wayland) and no one would have any incentive to create drivers for Wayland anymore. Everyone would just concentrate on developing Android drivers because that would be less work for them.
Didn't Canonical just say they don't want to support Android apps natively in Ubuntu because it would disincentivize developers from developing native Ubuntu apps? How is it any different with drivers?
Comment
-
Originally posted by BO$$ View PostSo apparently the wayland amateur kid devs are gonna get their ass handed to them when a real company does it as it should be done. Why do you think that Google does its own thing? Cause the amateurs were good enough? Admit it, amateurs in their free time cannot compete with a behemoth like canonical or other even bigger names. Everybody starts with a free software project and then diverges to meet the needs of the market, the real needs, not what those kids in their bedroom think that the market wants. Wayland is dead on arrival. Nobody wants it or supports it. The biggest names in the industry don't care about it. And don't tell me about Intel. Intel just throws anything to the wall and hopes something will stick to it. ARM is kicking their ass in the mobile arena and they are desperate.
Comment
-
Originally posted by BO$$ View PostSo apparently the wayland amateur kid devs are gonna get their ass handed to them when a real company does it as it should be done. Why do you think that Google does its own thing? Cause the amateurs were good enough? Admit it, amateurs in their free time cannot compete with a behemoth like canonical or other even bigger names. Everybody starts with a free software project and then diverges to meet the needs of the market, the real needs, not what those kids in their bedroom think that the market wants. Wayland is dead on arrival. Nobody wants it or supports it. The biggest names in the industry don't care about it. And don't tell me about Intel. Intel just throws anything to the wall and hopes something will stick to it. ARM is kicking their ass in the mobile arena and they are desperate.
Comment
-
-
Originally posted by plonoma View PostTheir approach seems to not fragment the driver scene for once (being able to use android and mesa open source drivers).
Originally posted by rafirafi View PostI think they want to be compatible with surface flinger so they can use proprietary drivers without spending any resources, this is not possible with wayland.
Originally posted by rafirafi View PostThat's let the tablet market but they don't have the leverage to get the gpu makers to do drivers for us (users of xorg and maybe in the near future wyaland)
Originally posted by newwen View PostBeing compatible with Android graphic drivers will surely bring some closed source vendors onboard, namely AMD and NVIDIA.
Originally posted by newwen View PostThis would force Red Hat to make a move.
Originally posted by zanny View PostIf they aren't bullshitting, and in October they have a shippable product under GPL that supports drivers from both X and Android, while having a more refined input model
Originally posted by newwen View PostEven Google wich has a hard bet on ChromeOS would have to switch to MIR.
Originally posted by Ericg View PostDaniels, if you're reading this thread, can you explain that portion of the article to us?
Originally posted by 89c51 View PostBTW could someone explain how they support the android graphic drivers by design and why this cannot be done with Wayland??
If you ask me, it was going to happen anyway. Canonical don't have any interest in co-operating with the wider open source community; it's in their interest to keep everything as closed and Ubuntu-specific as possible. Just look at them and GNOME. *shrug*
Comment
-
Originally posted by daniels View Post... with copyright assignment. You can't contribute unless you agree to sign over all your rights to Canonical.
Comment
-
Originally posted by daniels View Post... with copyright assignment. You can't contribute unless you agree to sign over all your rights to Canonical.
Comment
Comment