GNOME 3.12 Makes Further Wayland Inroads

[pingufunkybeat]

Qt 5 has only been "ready" for the stuff KDE needs since 5.2 (which isn't even out yet). KDE devs have made a huge amount of progress with the modularization for frameworks 5, but that isn't even done yet, and after that is done there are still going to be some API/ABI cleanups (if I understand the planning document correctly). So they have come a long way, but KF5 is not "ready" yet, which is why there hasn't been as much effort yet on porting applications (it is hard to port to a moving target).

I meant ready for Wayland.

KF5 are clearly aren't ready for everyday desktop usage, no argument there.

[bkor]

On the looks front, I prefer GTK. It is a little easier on the eyes, I think, and has really really really nice themes.
But the incompatibilities between freaking minor version numbers is so wrong it's not even funny.

GTK+ has a stable ABI and API between major versions. I'm guessing you're talking about themes, there is no ABI/API for themes. They obviously will need work between minor versions. Work that we're making easier by allowing more and more to be done via CSS.

[bkor]

A major new feature like this belongs in a new major version. What Gnome does is simply unprofessional? but so is using client-side decorations and GTK.

Major versions are decided upon by the release team, which you're welcome to join. FWIW, we rely on loads and loads of new technology during any major release. This happened many times during 2.x timeframe. Further, X support is not going away. All these version numbering discussions are rather amusing.

Anyway, version numbering is not related to proffesionalism. E.g. Firefox/Mozilla, Google, Microsoft, etc all have various similar examples. Meaning, you're suggesting nobody is professional, doesn't make much sense.

[TheBlackCat]

From what I can tell, Qt5, KF5 have been ready for a long time, and Plasma and KWin are getting there nicely.

Qt 5 has only been "ready" for the stuff KDE needs since 5.2 (which isn't even out yet). KDE devs have made a huge amount of progress with the modularization for frameworks 5, but that isn't even done yet, and after that is done there are still going to be some API/ABI cleanups (if I understand the planning document correctly). So they have come a long way, but KF5 is not "ready" yet, which is why there hasn't been as much effort yet on porting applications (it is hard to port to a moving target).

[Daktyl198]

A major new feature like this belongs in a new major version. What Gnome does is simply unprofessional? but so is using client-side decorations and GTK.

I agree with you, but GTK wasn't always that bad. If you remember correctly, it isn't even "Gnome Tool Kit", it's "GIMP Tool Kit". It has simple beginnings and could have been great, had Gnome not picked it up and ran with it in the COMPLETELY WRONG DIRECTION.

On the looks front, I prefer GTK. It is a little easier on the eyes, I think, and has really really really nice themes.
But the incompatibilities between freaking minor version numbers is so wrong it's not even funny.

[Awesomeness]

I think that another reason is that KDE is timing their Wayland support to coincide with the next major release, and this upcoming new version is not as visible or widely used yet.

From what I can tell, Qt5, KF5 have been ready for a long time, and Plasma and KWin are getting there nicely.

A major new feature like this belongs in a new major version. What Gnome does is simply unprofessional? but so is using client-side decorations and GTK.

[pingufunkybeat]

To be fair, there is more visible progress in GNOME, partially because Red Hat and Intel have a direct coordination with distro release goals (Fedora 21 or 22) but the support was clearly marked experimental and users wouldn't really come across it at all unless you go out of your way to install and tweak things. That is just normal "release early and often" approach in open source development. There is certainly some level of competition but the issues discovered and communicated with Wayland developers will help other desktop environments like KDE since common bits are being split out into their own libraries.

I think that another reason is that KDE is timing their Wayland support to coincide with the next major release, and this upcoming new version is not as visible or widely used yet.

From what I can tell, Qt5, KF5 have been ready for a long time, and Plasma and KWin are getting there nicely.

[RahulSundaram]

Gnome only seems to be "ahead" with Wayland support because they released a buggy version of it in 3.10.

To be fair, there is more visible progress in GNOME, partially because Red Hat and Intel have a direct coordination with distro release goals (Fedora 21 or 22) but the support was clearly marked experimental and users wouldn't really come across it at all unless you go out of your way to install and tweak things. That is just normal "release early and often" approach in open source development. There is certainly some level of competition but the issues discovered and communicated with Wayland developers will help other desktop environments like KDE since common bits are being split out into their own libraries.

[Daktyl198]

I would really like for KDE to catch up to GNOME with Wayland support.

Gnome only seems to be "ahead" with Wayland support because they released a buggy version of it in 3.10. KDE will have a FULLY WORKING and STABLE Wayland KDE working come summer... and I'm sure Gnome will have a FULLY WORKING and STABLE Wayland Gnome around the same time. It's not really a race against each other, more of a race to just get it done so that driver people start making EGL drivers.

Luckily, my only laptop uses Intel graphics so I can switch to Wayland as soon as either one is finished

[r_a_trip]

I would really like to run Wayland with nvidia proprietary drivers on 64bit system.

I would really like to run Wayland with nvidia developed foss drivers (on par with the other platforms) on 64bit system.