Linked by Moochman on Sat 2nd Dec 2017 00:06 UTC
Ubuntu, Kubuntu, Xubuntu

Ars Technica once again provides us with an in-depth Ubuntu review:

If you've been following the Linux world at all, you know this has been an entire year for spring cleaning. Early in 2017, Canonical stopped work on its homegrown Unity desktop, Mir display server, and its larger vision of 'convergence' - a unified interface for Ubuntu for phones, tablets, and desktops.

And now almost exactly six years after Ubuntu first switched from GNOME 2 to the Unity desktop, that has been dropped, too. The distro is back to GNOME, and Canonical recently released Ubuntu 17.10, a major update with some significant changes coming to the popular Ubuntu Linux operating system.

In light of the GNOME switch, this release seems like more of a homecoming than an entirely new voyage. But that said, Ubuntu 17.10 simultaneously feels very much like the start of a new voyage for Ubuntu.

Thread beginning with comment 651695
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[21]: No difference
by kwan_e on Wed 6th Dec 2017 10:01 UTC in reply to "RE[20]: No difference"
kwan_e
Member since:
2007-02-18

I'm fed up with FOSS pretending being the panacea


Yes I know that's your agenda. That's why I understood no reason will ever be good enough for you. A bug open for eight years? Laziness. Oh, someone has actually been working on it? Still laziness. Any answer anyone could have been given and you won't accept it.

Because you're not interested in facts. You're just interested in pushing your talking point.

And you keep excusing open source projects


No I'm not. I'm arguing this specific case which you won't ever accept any answer other than laziness.

Just like your freetard brotherhood.


You lose.

Reply Parent Score: 2

RE[22]: No difference
by Kochise on Wed 6th Dec 2017 10:22 in reply to "RE[21]: No difference"
Kochise Member since:
2006-03-03

Not only it took more than 8 years for someone start taking considering the bug, but even though it looks like someone is working on it and submitted a patch in July, more than 4 months back and still not into the main branch ? Should I consider it included in 2020 ?

The bug resolution is so slow in the open source community, that is obviously so scarce in resources, than someone else opened a related bug more than 6 years after the first that is still officially unresolved and remaining open.

And yes, since you still haven't provided me with VALID reasons for not involving more resources into bug tracking and resolving, I'm not going to accept your petty remarks and snarky tags to keep avoiding addressing the main issues.

Reply Parent Score: 2