Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

KDE Plasma 6.0 Is Enabling Wayland by Default

phoronix.com

Post reply on HN
Print view View original

81–90 of 202 posts

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#81

Post by sanitycheck »

addicted wrote: post #30
Pannoniae wrote: post #22

Earlier quoted context omitted.

Your comment is funny because Comic Sans is actually pretty good from a design and accessibility perspective. The complaints are mostly "fun fonts are not appropriate for a business" and everyone jumped on hating it. But those who are not that stuck-up don't hate it with a passion...

There you go proving that it’s not just that many Linux users have a bad design sensibility, but worse, they will defend bad design as good design. Not only do you defend it, even your defense proves that Comic Sans is a bad design, because matching the needs of what it’s used for (in this case a business setting, where fun fonts are not allowed) is one of the highest factors in good design. And you display another b…

> 1. Have bad design ideas. 2. Defend those bad design ideas. 3. Insist users and the people who want better design are wrong.

Not sure if you're right or not about Linux, but what you've laid out there has been Apple's approach for the past 20+ years and it's been working out pretty OK for them!

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#82

Post by johnchristopher »

bee_rider wrote: post #79
smallerfish wrote: post #23

It's been kind of buried, but KDE has the first steps of tiling mode built into it now, in addition to the default screen edge tiling (on KDE 5.27.8 on up). Meta + T to enable tile editor. Shift + window drag to move a window into a tile. Hopefully a lot more coming, including different layouts per virtual desktop & full keyboard nav for the tiles. But it's a decent start.

More tiling managers is always great! The advantages of tiling window managers are so tied to muscle memory, I’m not sure many people will want to switch from, say, sway or i3 or whatever. But at least new people will be able to give it a try. I’m not sure how much work is involved in replacing the window manager inside a desktop environment. It would be nice to just drop sway into kde. Dunno if that is possible thou…

> The advantages of tiling window managers are so tied to muscle memory, I’m not sure many people will want to switch from, say, sway or i3 or whatever.

Hear, hear !

I have been stucked with awesome for years now and even though I lost some functionalities between v2 and v4 I still can't switch. I tried i3 and regolith (was really looking for all the niceties of a DE: volume, bluetooth, screen, etc.) but tiling operations are not the same.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#83

Post by cout »

wasmitnetzen wrote: post #64
cmplxconjugate wrote: post #16

Earlier quoted context omitted.

I absolutely agree. It is functional and stable, but my gosh I can’t stand the design. The oversized top decoration for windows as well as the extremely poorly rendered pop-up for hovering over elements on the task bar.

You know can change that, right? One major point of KDE is that you can configure anything.

I remember when gnome was that way. I still don't understand why it changed.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#84

Post by brabel »

brnt wrote: post #6
mvelbaum wrote: post #4

KDE is pretty feature-rich, but it is just ugly. Look at the poor use of spacing/margins, the ugly black & white icons, the ugly font, the square edges, and just the overall look & feel. It needs a major face-lift. I dislike the attempts to dumb down GNOME but KDE being ugly makes it really hard to switch to.

Excellent spacing: no useless wide margins. Stylish icons that can blend in with various themes, which are clear and easily distinguishable. Font: most distro's actually default to Noto, not KDEs own. But you know what: this you can change, KDE didn't remove any and all options for customisation after all. You can pry Plasma out my cold, dead hands. Gnome, Macos, and Windows: now that's amateur hour.

I use KDE and MacOS on different laptops. Even though I like KDE , I find that compared to MacOS, KDE is the one that comes out a bit amateurish... the attention to detail in the MacOS UI is just amazing. Am I missing something?? How is KDE better (it really feels much more raw to me, but being on Linux I don't really expect much more)?

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#85

Post by dheera »

lxe wrote: post #72

Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.

Also, Chinese input breaks in Chrome on Wayland and they still haven't fixed this bug after 2+ years.

Also, Nvidia drivers don't work with Wayland.

So I'm still stuck with Xorg.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#86

Post by TillE »

j1elo wrote: post #53
theHamsta wrote: post #13

Earlier quoted context omitted.

They mentioned that the culprit for those additional load times was loading all the search backend for their application launcher which they deferred to the moment when there was actually the first search query (still shouldn't take multiple seconds)

I'm surprised they didn't go to a more clever solution such as "start loading it as soon as the most core components have already loaded, and CPU usage falls below 30% during 3 to 5 consecutive seconds". That'd seem to me like a sweet spot between what was before (making the whole system startup slower), and what you mention will be now (probably making the first search to load noticeably slower).

With modern hardware and OSes the ideal answer is typically to run non-essential tasks exclusively on efficiency cores. So you leave the performance cores free to handle stuff that the user immediately cares about.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#87

Post by Zardoz84 »

mvelbaum wrote: post #4

KDE is pretty feature-rich, but it is just ugly. Look at the poor use of spacing/margins, the ugly black & white icons, the ugly font, the square edges, and just the overall look & feel. It needs a major face-lift. I dislike the attempts to dumb down GNOME but KDE being ugly makes it really hard to switch to.

You know that changing everything that you dislike from the default theme, can be done easily.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#88

Post by TillE »

dheera wrote: post #85
lxe wrote: post #72

Wayland doesn't fractionally scale chrome, discord, vscode, spotify, beeper, and other appimage and non-native applications. So even if KDE enables it by default, most users will have to switch back to X.

Also, Chinese input breaks in Chrome on Wayland and they still haven't fixed this bug after 2+ years. Also, Nvidia drivers don't work with Wayland. So I'm still stuck with Xorg.

Wayland not working with NVIDIA is a massive deal-breaker.

I've used Linux desktops on and off for the past 20 years, and it's incredibly frustrating how everything is perpetually in a state of semi-brokenness as they move on to the Next Thing. I still think about the early years of KDE4, which were a horrible regression from the stable and usable KDE3.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#89

Post by esquivalience »

smallerfish wrote: post #23

It's been kind of buried, but KDE has the first steps of tiling mode built into it now, in addition to the default screen edge tiling (on KDE 5.27.8 on up). Meta + T to enable tile editor. Shift + window drag to move a window into a tile. Hopefully a lot more coming, including different layouts per virtual desktop & full keyboard nav for the tiles. But it's a decent start.

Thanks for this. As a new user of Ubuntu I stumbled into the meta-T shortcut but couldn't find out how to take advantage of it. Shift-T is what I was missing. I didn't have the terminology I needed to search effectively either.

Re: KDE Plasma 6.0 Is Enabling Wayland by Default

#90

Post by vlovich123 »

I enabled wayland recently and there’s been a lot of annoyances to the point that I wonder why I bother considering X11 works without these issues. For example:

* Chrome needs a bunch of extra flags to launch in Wayland mode

* Firefox needs extra flags to launch in Wayland mode

* Xwayland is just broken on Nvidia with both sides refusing to compromise (implicit vs explicit synchronization - Nvidia refuses to add implicit and Xwayland refuses to take Nvidia’s patch to do explicit). What this means is that you get tearing, flickering and all sorts of terrible graphical artifacts

* Chrome only just fixed HW acceleration for Nvidia (latest m120 beta)

* enabling vulkan causes Chrome to fail to render (although this may just me needing to try reinstalling Nvidia drivers)

* I thought it was an acceleration thing, but even with HW acceleration fixed Chrome has a bug where the mouse pointer leaves behind white speckling when mousing over on a dark background. VSCode doesn’t have this issue.

None of these issues appear in X and this is from someone who thought Wayland is the right way to go (eg you didn’t see this kind of story on Mac when they switched to HW accelerated compositing).

Post reply on HN