Originally posted by TheOne
View Post
Announcement
Collapse
No announcement yet.
MATE Developers Are Considering Mir-Over-Wayland
Collapse
X
-
Originally posted by tigerroast View PostI read the title and and all I could think of whas, "Huh?!!?" In the end though, this kind of makes sense. MATE has no Wayland compositor.
The whole point is to have someone else develop the compositor, so the only work to be done is have Mir work on MATE with little-to-no issues. Mutter is out of the window because MATE devs hate GNOME 3.
Originally posted by bregma View PostEven if they broke down and used Mutter at the other end of the client-server socket because it already supports Wayland, they would need to do a whackload of customization to Mutter and the client libraries to get the same functionality already supported out of the box by Mir. The entire philosophy of clients doing their own decorations and window management that is at the heart of Gnome3 is functionality the opposite of what Gnome2 did.
Originally posted by Luke View Postswitched to Cinnamon because I could get everything into one panel.
Originally posted by BaronHK View PostKDE has issues. For example, their SDDM login manager […] KDE is rotting from the inside out.
You can’t even troll right…
- Likes 2
Comment
-
Originally posted by Mystro256 View Post
Assuming I'm not misinformed in how GJS works, I feel like gnome should have a AOT compilation for JS scripts. I don't exactly imagine the JS scripts changing often enough to justify using JIT every time, at least with the scripts provided by the distro, i.e. in /usr. Plus, the distros can bundle in AOT binaries into the gnome-shell packages. Less CPU use, less power use, likely faster start up: I see no disadvantage to this.
Comment
-
Originally posted by Awesomeness View Post<snip>So exactly like Gnome with https://github.com/jderose9/dash-to-panel/ but fewer people working on it?<snip>
The way I ended up hacking on MATE was simple: in fall 2014 I ran a mix of MATE (gtk2 version) and cairo-dock and was not satisified with either. Whether MATE got GTK3 working or cairo-dock gained a true window list (with the named buttons) first would decide which way I went, and MATE was ready first and with better applets.
Comment
-
As for using Mutter, Mutter in X is a fat pig with poor performance compared to compiz and was even worse in the old days. In 2010 it was so bad Ubuntu did the massive amount of work in porting their Unity interface (now dropped) from Mutter to Compiz. Compiz is so complex it would be a nightmare to port to Wayland but if some high priority compiz plugins (e.g cube, expo) could be re-implemented in a wayland compositor (such as this Mir port) that would be a damned nice development and perfect for MATE.
Comment
-
Originally posted by Luke View PostThat actually exists, I think GNOME calls it the classic mode or some such thing
Originally posted by Luke View PostNo matter how big your system, you are saving CPU cycles and probably electricity as a result.
Comment
-
Originally posted by Pajn View PostBecause that example implements a full compositor with all features a modern desktop like MATE needs?
Oh, and it's fully tested just like Mir right?
Originally posted by Pajn View PostIs the MIR hate so strong that people actually prefer MATE to use a bare minimum weston based compositor [...]
- Likes 1
Comment
-
Originally posted by Awesomeness View PostSDDM is not a KDE project. It doesn’t have anything to do with KDE. It’s a 3rd party display manager whose maintainer the developer of Liri, a totally different desktop environment that’s competing against KDE and Plasma.
You can’t even troll right…
In fact, the KDE developers even recommend it over KDM.
Four years ago, when Fedora made the switch, it said "As of July 2013, KDM's maintenance consists of bugfixes for the most painful bugs, consisting of only about 20 actual commits to the repository in last two years (excluding translation, themes and merges), adding many new features would require major changes to a lot of the code and there is no active maintainer."
SDDM sucks as bad as the rest of KDE. KDE is just somewhat broken on HiDPI and you can fix part of it yourself. There is no "Oh, this is a HiDPI display! Bam! Scaled that for you!".
And even when you do scale KDE itself, SDDM doesn't respect that setting, much less autodetect HiDPI like GDM does. And even after you scale KDE, its broken font scaling makes inline spell checking basically useless because it doesn't show the red underline when you make a typo.
I think that KDE is suffering from years of most distributions defaulting to some form of Gnome, which has a coherent release system and considers every component to be part of the whole. This whole KDE "Let's split everything up and make a bajillion combinations so bugs are hard to reproduce because like four people in the world use KDE software on Windows." thing is a laugh riot. When someone asks what version of Gnome you run, you can say "3.24.3" and they know what you are talking about. With KDE just devolving into a semi-supportable mess of packages, you have opportunities for things to break that only affects some users some of the time under some circumstances. Some form of inline spell checking not working has been going on in KDE now for over three years but the bug report is still a ghost town. KDE's bugzilla is becoming worse than Launchpad.
Comment
-
Originally posted by Awesomeness View Post[...]sign Canonical’s CLA[...]
The legal crap that I refuse to agree with is sort of secondary to the fact that their software never seems to work quite right or that every time they try to go their own way with something it ends up dying a horrible death. It's very ironic, because one of the sound samples that used to be included with Ubuntu was a reading of The Fox and the Grapes, and that's essentially the tone that Mark Shuttleworth's posts take every time some crap Ubuntu software flops. Nobody in their right mind would sign Canonical's CLA. Unity and Mir might have caught on if they were genuine FOSS projects, but all the distributions that tried to package them gave up because they refused to compromise the quality of the rest of the distribution to make packages fit in with Unity.
- Likes 2
Comment
Comment