How is Wayland “ready” when critical things like idk, non QT apps quiting when the compositor crashes (and thus losing progress!) are called a “non showstopper”
@klangcola I'm not commenting on whether ot should be a show stopper or not. Just that it will eventually come also for non-Qt apps with MRs from KDE contributors to other projects.
its not listed as one is the weird thing, because it totally should be
imagine drawing and suddenly your compositor crashes leading to your program to crash and you to lose hours of progress, but other QT programs are fine
should’ve used krita because that’s QT except you cant replicate your workflow in that program because it misses features (and also you dont like it)
This is a real scenario I would have to worry about. That’s a showstopper for me
@Zamundaaa@mnglw xorg Apps don't crash when the compositor crashes, you can just switch out compositors/window managers. But xorg Apps crash when the xserver is crashing
A huge issue I see is that it feels like Dolphin has memory issues at the moment. I get permanent background crashes for no specific reason (already reported).
And rewriting apps in Rust is not existent for Qt, as it uses C++ a lot as far as I understood.
I dont like the design of GTK, even though its more modern in a way, but there are already lots of GTK apps in Rust.
Somehow I think KDE is a bit doomed here. Its Qt or a complete rewrite which will not happen.
Do you know more about this? A big part also is that I often hear young Devs dont learn C and C++ anymore, but maybe prefer Rust if any low level language.
I love KDEs features, and I am very excited for Plasma 6, which will hopefully be a lot more stable and cleaned up!
I’m all for some good old Rust evangelism, but I think it’s a bit of a stretch to claim that KDE is "doomed"in the absence of a migration path to Rust, and it’s not obvious to me that moving to Rust is somehow a necessity for the long-term viability of a project.
To your point about young devs and C/C++, afaik C is still pretty standard curriculum for CS degrees at most colleges and universities. C++ maybe not so much, but I would argue that it actually has a shallower learning curve than Rust. IMO the STL is a lot easier to get a grasp on as a newer developer than Rust’s borrow checker or lifetime system.
IMO the STL is a lot easier to get a grasp on as a newer developer than Rust’s borrow checker or lifetime system.
I actually feel like Rust’s borrow checker is more difficult to learn for experienced devs. We’ve got a trainee in Rust and for her, it’s just a normal thing that variable slots hold ownership and can lend it and get it back. She does sometimes still struggle with when to clone and when to borrow, but she’s getting there.
As for the lifetime system, no one on our team really gets that one. 🙃
But (that’s because) you rarely need it.
no more frames within frames! Instead Breeze-themed apps adopt the clean design of modern Kirigami apps, with views separated from one another with single-pixel lines!
Does this talk about that little blue square that is inside of dolphin where the folders reside?
I would agree with that decision - Dolphin handles tabs very well and if the need ever arises for something like split view, I just hit ctrl + T. Feels more natural to me.
The double-click speed setting returns, and now lives on System Settings’ General Behavior page. Before you ask why it’s not on the mouse Page, it’s because it affects touchpads too and that has its own page, and duplicating the setting on both pages seemed messy and ugly
As long as the value is synced, I can’t imagine how it would be bad to have in both pages; especially since that’s where a user would expect to see it.
There’s nothing wrong with multiple ways to find a common setting
I think the best solution is to have a… Link? To the general setting.
Having duplicated settings across multiple settings page is something that I think is an issue. Cause it isn’t obvious to the user if the setting is actually shared between the two pages or if it has two different options with the same name. It also doubles cognitive load to the user, as if they have a Touchpad and Mouse they need to remember both pages have the same setting.
A link is more of a way for the designers to tell the user “Hey, we know what you are trying to find, but it is in another place”
Great news regarding the reorganisation of System Settings. I am skeptical about the sorting however? Why put “Internet” first and “Appearance” so low? Seems to me the later is often the first thing people look for in Settings (and thus often first, or near the top, in most settings).
It might also just be what people are familiar with on other systems. On iOS, macOS, Android and windows, the wifi settings are usually at the top. So it makes sense for KDE to do the same.
My impression was that it was more common to have stuff like “Appearance” first, but you seem to tbe right. At least on my Android phone, network is the first item indeed. I guess I’m getting old!
Haha, I guess Wifi just requires you to go into the settings more often than something like appearance, which you usually set, and then rarely come back to.
@mokazemi combining the overview and desktop grid is fantastic. If it’s anything like how GNOME lays out workspaces, it might just make me switch to kde :)
pointieststick.com
Hot