All Things KDE/Plasma-6 for Slackware Users.
Starting a new thread for KDE-6 would seem, to me, to be appropriate. :)
Quote:
|
Ooh man, I remember it as not ago that we were at the same place in regards to KDE5. I was excited about the release, as KDE4 was promising, but KDE5 would be the "perfection" of KDE4. I was not going to jump right into KDE5, but wait some releases for it to be more stable first. In the beginning it lacked many of the features I expected from KDE, so I was quite annoyed with it, but I did expect it to incorporate those features again during some releases. It did, but quite slowly.
I've been using KDE since KDE3 at least, probably before that as well, but I can't quite exactly remember. It's quite a luxury desktop, best on the market IMO. However, I'm quite disappointed too. With all the balls KDE had in the air, with plasma-active, plasma in general, kde for netbooks and various formats etc, I was really hoping it would be a more modular desktop that scaled well from mobile UI to full multi screen desktop UI. But it never really did that, despite plasma. It kind of turned into 4-5 different development platform, 1 for each format, and the desktop plasma/kde was not at all modular, but rather integrated with everything depending on something else and whatnot. I was kind of hoping for a Plasma desktop that you could scale from being a windows manager to a full desktop environment, to fit in with all the other scaling I was hoping for. But despite that looking like the direction they were initially taking, it didn't pan out, and I was quite disappointed. I don't have great hopes this will happen for KDE6 either, but on a positive note, it should be the first KDE desktop version fully compatible with Wayland. I guess we could call it the Wayland version. Having read some KDE development forums, it seemed pretty clear that it wasn't possible to split kwin into kwin-wayland and kwin-xorg, so instead they had to just add the wayland stuff to the already existing codebase. I'm already using Wayland, so I'm quite happy to see them go "all in" in regards to Wayland with KDE Plasma 6, but I would be even happier if they did the scalability/modularity thing. Call me old fashion, but I'm a bit weary about the trends within KDE, in terms of some rather strange ideological directions, and inclusions of software that to many is untasteful and many will delete immediately. I don't really want a desktop that keeps track of everything I do, and set up various internet facing daemon/service like things. It goes hand in hand with modularity, and those things should be more kind of opt in than default configurations, which brings us back to dependencies, and the whole cycle again. But well, I can delete that stuff, and I don't need to care about what kind of opinion people who make KDE have, so I guess I'll just have to live with the most powerful desktop on the market, that also happens to be rather pretty. Every GUI designer need to learn from KDE, this is professional workflow stuff, and many of those things that KDE do, really ought to be minimum requirements for any modern or decent desktop. Sadly, that's not the case, which makes most other desktops look rather antiquated by comparison. Not just for personal use, but KDE methods of managing windows and behaviours and all these kind of things is perfect for a professional workflow. Instead people have to fight with their desktop and be slowed down by clunky behaviours and desperately outdated window management in things like Windows. ffs, they didn't even manage to properly make multiple virtual desktops yet. |
Member Response
Hi,
Alienbob has announced; KDE: February 2024 MegaRelease Quote:
Hope this helps! :hattip: |
I'll guess that Pat will depend on Eric's testing to decide when to merge KDE 6 into Current.
Not that I zealously follow KDE news, but my understanding was KDE 6 was supposed to be a roll over of KDE 5 to Qt 6. Seems now that new features and twists are being added to KDE 6. I am still rooting for KDE 5.27.x in 15.1. Might not be be a public relations coup releasing 15.1 with 5.27.x, but 15.1 would avoid similarities to what happened with the KDE 3 to 4 transition. Considering Pat averages about 7 years of support with each release, 15.1 with 5.27.x would allow many users to just sit back and breath for several years without playing the relentless updating game. Well, I can hope and dream. . . . |
Mark
|
Quote:
The look and feel is basically the same of kde5, mostly some polish, little changes to default settings and more plasma components ported to QML (which i don't personally like). Comparing to the kde3->kd4 and kde4->kde5 transitions it's really not that much different |
Quote:
|
Quote:
|
Quote:
|
Quote:
Applications, regardless of the widget set, are all that matters. The desktop should be visible only at startup. I use Krusader, and I consider it a real shame I have to install a metric ton of KDE garbage for this one application alone. |
Quote:
But it certainly is not without its flaws. There is another thread here currently where people who use XFCE are finding that it leaves stale sockets in /tmp, where they accumulate and can cause problems if there are multiple users on the machine using XFCE. A Google search shows that this has been impacting XFCE users since at least 2005. It also happens under the BSDs. Quote:
You might not like all of the bells and whistles. You might consider it to be bloat. But there is no denying the fact that it is a quality product. Quote:
|
Quote:
|
Quote:
Quote:
Yeah, I agree, like I said earlier about KDE modularity and dependencies, it never really panned out like it initially looked it would. That kind of goes for interoperability of desktop programs and features too. Quote:
|
Quote:
Pat has been in this situation previously with selecting a distro release date despite some notable software package "big" release being imminent. Not directly related but the Debian developers go through this decision making too with each release cycle, often choosing older versions of software rather than bleeding edge. KDE 5.27.x is stable. KDE 6.0 might or might not be as stable. Moving Slackware 15.1 to Qt 6 affects SBo maintainers too. Perhaps Eric's ktown testing will prove 6.0 stable and robust. Eric has more than half a clue. With or without KDE 6.0, the 15.1 development cycle is looking to be about two years. I suspect with all of the complexities of modern software and dependencies, Pat probably would find a two year cycle to be palatable. While always fun, speculating on a 15.1 release date is futile until the Current change log announces major GRUB changes and demotion of Lilo. One thing Slackware users can rely is 15.1 will be stable one way or another. I am leaning toward wanting 5.27.x, but if Eric can pull a Bullwinkle rabbit out of the hat with his ktown testing, then I expect KDE 6.0 to be stable and not disruptive. |
Quote:
The full article can be found at, https://pointieststick.com/2023/11/1...een-recording/ |
All times are GMT -5. The time now is 07:41 AM. |