/tech/ - Technology★

Plasma is fine

wrong thread btw

>>859584 (OP)

I don't understand what you're asking.

KDE is, and will always be bloated, because it's trying to be a "complete" desktop operating system with absolutely everything you'd ever need. It's great if you want something comparable to popular commertial OSs.

As for memory leaks, I don't know, but then again, I've never been able to tell. What I do know is that you won't gain anything by running old, unsupported versions. Just run the latest and report whatever bugs you find.

>>859586

I read a while ago they were trying to make the installation leaner by restructuring the dependencies so a minimal KDE installation pulled less packages.

>As for memory leaks, I don't know, but then again, I've never been able to tell.

It's had leaks for as far as I can remember.

I use Plasma on Fedora and have been pleased. Reliable and not too bloated.

Bruh. With PoetteringAudio eating a whole gig of RAM, multiple open chromium instances and a decently bloated suite of audio effect tools for listening to music from my Electron-based player in highest Satan Maximised glory, my system uses 2.5GB of RAM in total. There's barely barely any space for Plasma services within that amount. After a fresh boot, this system takes up 450MB. It's pretty safe to say Plasma is not bloated and does not leak memory.

>>859587

>I read a while ago they were trying to make the installation leaner by restructuring the dependencies so a minimal KDE installation pulled less packages.

The default install still pulls a lot of packages. What they've made leaner is installing a single KDE app when not using the DE. They've redesigned a lot with KDE 5, but only really with reducing old cruft in mind.

>It's had leaks for as far as I can remember.

I'd chalk it up to placebo. Any major leaks are easy to pin down and get rid of. Smaller ones are just not noticeable. It's never really been too bad as far as I've used KDE back in the days of 4.x.

It uses fewer resources than Gnome 3 while having loads more functionality, but it's still fat compared to most Unix DEs.

>>859589

Not to hijack the thread but why was PulseAudio mass adopted when JACK exists?

>>859604

JACK is a pull-driven API with no stability guarantee, it's shit to program for, it's shit on CPU usage because it wants to use tiny buffers, and the current version has a hard dep on dbus

>>859604

I think JACK simply came later, and it's more targeted towards professional audio shit rather than generic consumer audio playback. I actually use PulseAudio as a JACK client so I can get both good compatibility as well as JACK's manual connection system and generally better control of audio streams.

>>859584 (OP)

Plasma