132
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 11 Nov 2023
132 points (97.1% liked)
KDE
5207 readers
161 users here now
KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
Plasma 6 Bugs
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
founded 1 year ago
MODERATORS
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.
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.
Qt_Bindings_for_Rust