I suggest that you run Arch in a VM; that's what I'm doing. Slackware64-current is not a pain compared to Arch. Trust me on this one. Slackware64-current is much less likely to break than Arch.
Back on topic folks. I can wait for 15.0. We have a stable 5.15.x kernel, KDE-plasma is looking good, and just a bit more polishing and we're good to go I'm guessing.

3 members found this post helpful.

For now, we probably have the best KDE/plasma5/Wayland integration, after OpenSuse

Let's hope this never happens

2 members found this post helpful.

Yes, impatience. It's *EXACTLY* what *YOU* are showing the world *YOU* are made of.

How's this...if you're tired of waiting, go make your own distro...you seem to think there's nothing to it and people making demands on you to 'get it done now!' are the 'good' people of the world who will volunteer to help you out with it.

We realized you were easily amused at your first post. The 'anything shiny immobilizes the brain' type.

2 members found this post helpful.

Sheesh...the ever present 'I have a need to make sure that everyone knows I'm leaving even though no one knows who that person is nor cares either way' type.

Don't let the door hit ya where ya sit, on the way out.

2 members found this post helpful.

This made me smile.

Probably. You made it to the release of Duke Nukem Forever.

1 members found this post helpful.

Agreed! But also the lack of communication by the main developer(s) about what their goals are for 15.0 (a check list, a to do list). How hard can it be to quickly update the website.

If y'all don't care about what I say, then maybe this will wake you up: invidious.snopyta.org/watch?v=ly24HLGyYPc @ 0:22:01 onward; specifically his comment @ 0:23:27. But just listen to all he has to say about Slackware. I completely agree with his sentiment.

3 members found this post helpful.

Just my 2cents US:

For those who would like to admonish some of us for a "lack of patience", I posit this: yes, patience is a virtue. But it isn't an unlimited resource. I would suggest taking a little bit of nagging of the kind "are we there yet?" as a compliment. It suggests that some of us are eager for a new Slackware stable toy to play around with. I've mostly kept these thoughts private among a couple of my fellow Slacker friends so as to not beat a dead horse publicly and annoy others.

And as a person who has been with Slackware for a VERY long time (since it basically became Slackware), I'm hoping that going forward we can see point releases more frequently than we have lately. And by that I'm meaning more than just a merging of patches back into the main install tree, but not really big enough changes to the OS to really consider it a major release. The reason I am hoping for this is that it might help us keep momentum. Even though it doesn't concern me that people laugh when they hear I use Slackware (I don't have to be on any bandwagon), I think this would be a good way to help shore up the community around Slackware. I fear we might have shrunk further with such a long stretch between releases that we've had between 14.2 and 15.0. We're not dead yet. (clang!) But I think we're eager for some excitement. :-)

5 members found this post helpful.

Yes - DEs are overrated. Just use a Window Manager and install addtl. tools as needed (dzen, dmenu, etc.).

Well - We don't know that. Until we know what the goals are for 15.0. If he is indeed waiting for some kde stuff then Yes, I'd agree. But if he's waiting for ... then ...
Ratpoison ...

2 members found this post helpful.

If current is ready, just use it. Why does it have to be called 15.0?

I've never seen a Linux distribution where the users, or random people making videos, decide when to put a release out...

2 members found this post helpful.

Because of 2 GB updates which can make your system unusable. If there custom setup on top part of it needs to be reinstalled. You can only use current as it is. Perhaps adding small customization. Beyond that it is waste of time to customize system for own needs. I am not in the mood to constantly repair broken things. We use current for some purpose because there is no stable. Not as replacement.

3 members found this post helpful.

Which, if that were the case, would indicate that a release may be a bit further ahead than you seem to think...?

2 members found this post helpful.

As expect something like that running current. I will be running current in hope to provide feedback. As frugal and in VM's. My hardware is so old that really installing current separately dual-boot with stable has no benefit. But for reasons Torvalds will create superstar kernel. Things happen. Or KDE team will create bug-free desktop. I always mistake aconadi with anaconda - snake Fedora installer. And IMO Fedora is so bad. Cheapest testers all other the world. At least RH may try to offer some financial contribution for best fedora users. Like games tournaments where you can earn real money. Imo it is just unethical. What RH is doing. People work hard for free only for RH benefit. And this sh...stuff they force others to use. Who needs systemd in VM?

You cannot infer by size of download what the distance from release is. A single 1-line change in the source code for 50 separate packages can result in 2GB of download of binary packages.

1 members found this post helpful.