SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Better that "when" to happen in the near future, "if" even happens...
If we still debate this "issue' for a year, or two, we will have the surprise that Plasma5 is already abandoned and obsolete, just like KDE4.
Or could be about a "when" like in "when the pigs will fly" or "when Jesus will return" ?
I remember why I put you on my ignore list, your contributions add no value and are nothing but abrasive. Mistake to clean out my ignore list, so there you go, back on. PLONK!
I remember why I put you on my ignore list, your contributions add no value and are nothing but abrasive. Mistake to clean out my ignore list, so there you go, back on. PLONK!
OK, I apologize for the claim that if Plasma5 will be merged, is better to be merged in the near future, certainly before its natural end of life.
we’re aiming to have Qt 6.0 ready for a first release by the end of 2020
That's only if the their aim is reached and I very much doubt that Pat will ship a .0 version just released. So Qt6 will certainly not be ready when Slackware 15 will be released if that happens in 2020, or even at the beginning of 2021.
PS Maybe Pat considers shipping Qt 5.15 LTS when it will be released and accordingly waits for that before releasing Slackware 15 and/or switching to Qt5 thus Plasma 5? Pure speculation, of course.
Last edited by Didier Spaier; 10-09-2019 at 04:14 PM.
If you read that, it strongly implies that KDE devs may not need to release "Plasma6" when QT6 is used, although they might need to do some tweaking...
Quote:
Qt 6 will be a continuation of what we have been doing in the Qt 5 series and should as such not be disruptive to our users. -snip- As described in more detail below, Qt 6 will aim for a large degree of compatibility with the Qt 5 series.
Our goal with Qt 6 has to be to better integrate with this functionality, without losing backward compatibility.
And further on they have a whole section about compatibility with QT5...
Quote:
Compatibility with Qt 5 and incremental improvements
Compatibility with older versions is extremely important and is a major requirement when we develop Qt 6. There are billions of lines of code written using our framework and any incompatible change we do will thus have a cost for our users. Furthermore, the more work the change to Qt 6 requires from our users the slower the adoption will be, which leads to more cost on our side to maintain the last version of Qt 5.
As such, we should aim to avoid breaking Qt in a way that triggers compile-time or runtime errors in our users’ codebase. If we must break compatibility, a compile-time error is preferable over a silent breakage at runtime (as those are much harder to detect).
While we do need to remove certain deprecated parts of Qt, we need to ensure that our users have the functionality they require. That implies that key functionality, such as Qt Widgets and other parts used by a large portion of our users, will, of course, stay available.
We are planning for many incremental improvements to our core classes and functionality that we could not do in the Qt 5 series. The aim is to keep full source compatibility, but as we can break binary compatibility with Qt 6, we can do quite a lot of cleanups and improvements that couldn’t be done within Qt 5.
Nevertheless, we need to move forward, and some house cleaning is required with Qt 6. We will remove most functionality (functions, classes or modules) that have been deprecated in Qt 5. This house cleaning will help free up our developers’ time in the longer term and allow us to have more focus on the maintained and current codebase.
Porting away from those deprecated parts does however need to be as simple as possible and our users can ideally do this incrementally using Qt 5.15 LTS. Our goal should be that Qt 6 is compatible enough with Qt 5.15 LTS so that one can easily maintain a large code base that can compile against both versions at the same time.
Distribution: Slackware/Salix while testing others
Posts: 1,718
Rep:
Quote:
Originally Posted by Didier Spaier
quote of the document you linked to:That's only if the their aim is reached and I very much doubt that Pat will ship a .0 version just released. So Qt6 will certainly not be ready when Slackware 15 will be released if that happens in 2020, or even at the beginning of 2021.
PS Maybe Pat considers shipping Qt 5.15 LTS when it will be released and accordingly waits for that before releasing Slackware 15 and/or switching to Qt5 thus Plasma 5? Pure speculation, of course.
Apparently you do not use MS Windows?
I have to use Windows 10 (and before that, Windows 7) at work and run KDE Plasma5 at home on desktop and laptop. I can assure you, Plasma5 does in no way look like, or behave like, Windows. Their respective UIX teams may have partly overlapping User Interface Guidelines but their implementations are vastly different.
Back when I first tried out your KDE5 (and don't get me wrong, I appreciate your work on KDE and everything else) I was hanging out on a Windows forum every once in a while and it was shortly after Windows 10 came out. (Pre-RTM)
There was a wallpaper that Windows was using that was like a field of snow with a path or something, and KDE had something similar. All I had to do was change the wallpaper on KDE to the Windows one, then I told everyone there that it was Windows 10, and everyone fell for it.
Literally the only thing that I did was change the wallpaper. The ugly flat monochrome icons (that for some reason are popular these days) were almost exactly the same.
But I mean that's not my only issue with Windows 10. I could go on and rant about it for hours, but I will spare everyone. (Policy, menus, ugly UI, etc.)
PS: I still have 2 desktops that run Windows 7, a laptop that runs Vista (my favorite Windows) and a laptop that runs Windows 2000. The Windows 7 desktops are used daily, the others, well not so much. I refuse to run Windows 10 on any of my hardware.
BONUS:
Last edited by Skaendo; 10-09-2019 at 07:34 PM.
Reason: spelling
There was a wallpaper that Windows was using that was like a field of snow with a path or something, and KDE had something similar. All I had to do was change the wallpaper on KDE to the Windows one, then I told everyone there that it was Windows 10, and everyone fell for it.
I think several people consider that the blocking factor for a new Slackware release is this big KDE5+Qt5 thing. They may think that without KDE, it would be easier to issue a release. They may be wrong -- we just don't know.
Now, regarding the negative impact on the Slackware Community, several users have highligthed that 14.2 doesn't work on recent laptops because of the ageing kernel. Some may want to switch to other distros to be able to use their new laptop, potential new users may decide to pass, considering KDE4+Qt4 and the lack of apparent movement, etc. (these arguments have been rehashed to death in other thread)
So yes, too long a release delay may also negatively impact the community.
The short comment by Pat ("not if but when") is already a precious bit of answer, and we all can see how just this has changed the tone in the thread. So I think a bit more info from Pat about what are the major delaying factors would help a lot.
Firstly, thank you for remaining gentlemanly while having a POV that is less than the majority. It's really easy to get defensive online and that you didn't deserves respect. You have some of mine.
I do need to ask a probing question however. Do you actually think installing and switching to another distro is easier and faster than compiling a new kernel?
I may be very biased since I compile new ones rather a lot which also means I haven't tried it but what's there to stop a user from trying a newer kernel from -Current in 14.2? AFAIK it should work just fine with only minor adjustments. Shoot! Even though I routinely have at least 4 working distros on my Main I'd sooner install a second copy of Slackware just to play with kernels and/or "slipstream" a new kernel into the install disk(s) than install and depend on a new distro for my Main.
As for prospective "potential new users", I'd wager given the "press" from the likes of just about everyone else out there including DistroWatch (whom you'd think would give respect at least for Slackware being the oldest "last man standing" and truest to original Linux concepts) that Slackware is old and hard, I seriously doubt the version of KDE and QT is going to be a deciding factor for them. Those that are seeking rock solid stability and understand Slackware is not designed nor maintained by committee (like everyone else) will still check us out and those that only care about "new and improved" (and probably "easy") will likely go to one of the *buntus or some rolling release.
I do need to ask a probing question however. Do you actually think installing and switching to another distro is easier and faster than compiling a new kernel?
For some people, probably. Distrohopping is a very widespread practice, and many people can install a distro but not do things that might be considered more "difficult" like building their own kernel. It's easy with a good guide to walk you through and a good config to start with, but many people don't know that, and the task may seem daunting at first.
Speaking of which, what happened to DUSK? Actually, anyone know what happened to Dave? I haven't heard from him in a long time. I hope he's okay.
Last edited by montagdude; 10-09-2019 at 11:20 PM.
I was about to add something to this discussion; but I don't have anything useful to add right now - just the fact that I am rather inebriated and I wanted to let that be known; - I don't care, this is my thread so I can do whatever I want .
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
.
