Live data from Hacker News

KDE's Plasma 5.2 – The Quintissential Breakdown

kver.wordpress.com

41–50 of 61 posts

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#41
post #2

Maybe it's a well-researched article, but am I the only one that bothers the structure of the website? I am not able to read it. The text is just in the middle, really big white space left and right. Than there is this big wallpaper on every page. By the way, why so many pages? Sorry for off-topic.

Ahh, okay, it seems to be fixed now. There was a fullscreen image on top of every site (you could not even see the headline!). The width looks good now, maybe it way just my high resolution monitor (UHD)?

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#42

Pleasantly surprised by: > Frameworks 5 and Plasma 5.2 form a fairly lean pair compared to historic KDE releases; This is mostly anecdotal and other factors are in play, but no matter how you slice it Plasma 5 uses less RAM, somewhere between 20-40% less RAM is consumed on a freshly booted machine, exactly how much mileage you’ll get out of it will widely vary depending on your system, configuration, and distribution…

> (on p3; is there a pages=all type URL hack for wordpress?)

If you have Safari its Reader View works. Unfortunately none of the “readability”-type bookmarklets I know of work in this case.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#43
post #26
post #3

It is because that the "best" apps for Linux distros are written with GTK the reason for KDE being much less mainstream than Gnome?

Slightly related, but can someone clear up for me (a person who occasionally administers a headless Fedora box but doesn't venture into desktop Linux land) how different WMs and distros work when I want to install a particular piece of software? Does a desktop application have to be specifically written to run in KDE or Gnome or Unity? Or does it just look funny if I try to run a K* application in Gnome?

They work fine. There's even some effort to make apps use similar looking themes and icons when running in a different desktop; certainly things like tray integration work pretty consistently. It's not perfect - they might look a bit funny - but apps from the "other side" stick out less than e.g. java apps always do.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#44
post #3

It is because that the "best" apps for Linux distros are written with GTK the reason for KDE being much less mainstream than Gnome?

I'd say more of the best apps are written for Qt. Certainly the only high-profile case I know of an app switching from one to the other was Rosegarden, which switched to Qt and found it to be a much better toolkit.

Part of the reason is history (if we're talking about 15 years ago then Qt had a more restrictive license - and, sad to say, the gnome website still spreads FUD about this, or did the last time I looked). But mostly I think it's that big distros have Gnome as the default - probably because it's easier to support since it's much less configurable than KDE.

(And I don't think it's a clear case of one being "more mainstream"; rather, my impression is that Americans tend to use Gnome/GTK and Europeans tend to use KDE/Qt)

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#45
> Third party high-DPI support for applications like Steam and Firefox will be much more mixed

Dude, Steam is still sucky on OSX/Retina, almost three years from release; and Firefox took its sweet time to get there as well (and it's still not perfect). It's not KDE's fault.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#46

Oi. I wish the nice designers of Silicon Valley could give some "pull requests" easily to the KDE team. The design is such a mix of things that don't go together -- some places of translucency, others don't, the pop ups are mostly flat yet the calculator has shadows, the search results and bookmarks have borders on every row yet the launch menu doesn't, the spacing between items in the left side of dolphin is off (to…

It's actually very easy to contribute to the design process. Especially for this entire redesign. It was announced right from the start on the website / blog, the mentioned Visual Design Group website was put up, they created a subforum for design discussion and input (very active and so easy that even I, a non-designer, was able to participate), and they regularly posted detailed updates on the design process asking for feedback (sometimes in the form of polls). So I'm not quite sure how much easier you are expecting the process to be.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#47
post #8

A big raised middle finger goes to the developers who thought it was a good idea to make it impossible to opt out of akonadi, nepomuk, baloo, activities, monochrome tray icons, that fucking cashew icon and having an additional separate colour scheme just for the task bar. All of KDE is configurable and can be switched off, except these "innovations". Still using KDE, because it's the least bad desktop environment, bu…

I agree with your sentiment, although I disagree with the way you said it. On the actual issues raised, most of them can indeed be turned off or at the very least mitigated some how.

Akonadi is indeed a resource hog and useless (a dozen processes and 100+MB memory usage). If you don't use any KDE PIM application (Kmail, Korganizer) or any calendar event integration they don't appear. Nepomuk is no more, replaced by baloo, which is actually pretty fast and light on resource usage, so I keep it running. But it can be easily turned off in the system settings under the desktop search item. I don't use activities, the only trace of it is a kactivitymangered process running, if it bothers you that much you can set up a startup script to kill it.

The tray icons and cashew you may have a point. Although I like monochrome status icons but the cashew is an eyesore, so I drag it underneath the panel and it stays out of the way.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#48
post #47
post #8

A big raised middle finger goes to the developers who thought it was a good idea to make it impossible to opt out of akonadi, nepomuk, baloo, activities, monochrome tray icons, that fucking cashew icon and having an additional separate colour scheme just for the task bar. All of KDE is configurable and can be switched off, except these "innovations". Still using KDE, because it's the least bad desktop environment, bu…

I agree with your sentiment, although I disagree with the way you said it. On the actual issues raised, most of them can indeed be turned off or at the very least mitigated some how. Akonadi is indeed a resource hog and useless (a dozen processes and 100+MB memory usage). If you don't use any KDE PIM application (Kmail, Korganizer) or any calendar event integration they don't appear. Nepomuk is no more, replaced by b…

But it's not a cashew anymore. It's a hamburger!

The article says "it drives tweakers nuts because it’s the one unchanging thing on the desktop. There have been heavy debates on how to hide it, but for the interim it’s here to stay." Really? You get the same thing by right-clicking (or long press on a touchscreen, I imagine) on the desktop. Having an omnipresent widget is redundant and annoys people who don't need it.

Except many inexperienced users (and some experienced yet lazy users who never take the time to learn their computer, I've noticed) don't know or often forget about right-clicking. So when you throw a bunch of random people who have never seen KDE before and test their proficiency with the desktop, of course they're going to overlook right-click menu and whine about needing a special widget for customization. But that's how UI design is these days: conceding to the lowest common denominator. Designers are striving for a utopian interface that can be used without any training or adjustment period. Yet it's a myth. It's impossible to make a computer that can be used without instruction. Maybe if half as much time was spent writing documentation as is spent twiddling with icon colors users would have a resource where they could learn how to use KDE. Then you could build a desktop that doesn't feel like it's in novice mode all the time.

Except documentation isn't as sexy as screenshots and Google-ripoff icons.

Addendum: "Authors note: My testing machine had an issue with activities, so I was unable to fully test activities: this section may have minor inaccuracies."

How much better off would KDE be if they just stopped foolishly hanging on to the idea of Activities? No one uses it. It's a solution in search of a problem.

Also, I told my non-techie brother that the three-line menu was called a "hamburger". He looked at me like I had a carrot growing out of my nose. Please someone come up with a better name for that thing.

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#49
post #26
post #3

It is because that the "best" apps for Linux distros are written with GTK the reason for KDE being much less mainstream than Gnome?

Slightly related, but can someone clear up for me (a person who occasionally administers a headless Fedora box but doesn't venture into desktop Linux land) how different WMs and distros work when I want to install a particular piece of software? Does a desktop application have to be specifically written to run in KDE or Gnome or Unity? Or does it just look funny if I try to run a K* application in Gnome?

Thanks for the clarification all!

Re: KDE's Plasma 5.2 – The Quintissential Breakdown

#50
post #47

Earlier quoted context omitted.

I agree with your sentiment, although I disagree with the way you said it. On the actual issues raised, most of them can indeed be turned off or at the very least mitigated some how. Akonadi is indeed a resource hog and useless (a dozen processes and 100+MB memory usage). If you don't use any KDE PIM application (Kmail, Korganizer) or any calendar event integration they don't appear. Nepomuk is no more, replaced by b…

But it's not a cashew anymore. It's a hamburger! The article says "it drives tweakers nuts because it’s the one unchanging thing on the desktop. There have been heavy debates on how to hide it, but for the interim it’s here to stay." Really? You get the same thing by right-clicking (or long press on a touchscreen, I imagine) on the desktop. Having an omnipresent widget is redundant and annoys people who don't need it…

> The article says "it drives tweakers nuts because it’s the one unchanging thing on the desktop. There have been heavy debates on how to hide it, but for the interim it’s here to stay." Really? You get the same thing by right-clicking (or long press on a touchscreen, I imagine) on the desktop. Having an omnipresent widget is redundant and annoys people who don't need it.

I usually use right click, but you know that you can customize your mouse actions on the desktops and set right click to other stuff, like showing a running applications menu ?

Post reply on HN