Also has to be said that KDE on those slower-moving distros is actually buggier than on up-to-date distros. I have to use Kubuntu LTS at work and it has so many more glitches and crashes compared to openSUSE Tumbleweed and NixOS on my personal laptop.
I get asked to relatively often at dayjob, but I keep telling them that we can’t do that…
Yeah, and you don’t have to know which fork to choose. Only the compatible fork will show up in the search.
(I was going to recommend that, but had something in the back of head, that you needed a manual step to enable the configuration. But I just saw that this is described in the Plasma 5 version, not the Plasma 6 fork, so I guess, it’s not necessary anymore…)
It is the first one, yes. Just the normal keyboard shortcut settings. And all the Krohnkite shortcuts are prefixed with “Krohnkite”, so you can find them easily.
I believe, that’s something which became impossible with Wayland?
But it wasn’t very good under X11 either. Even back then, it was much less clunky to use the various KWin scripts, which offer tiling. Well, and by now Plasma has built-in semi-automatic tiling, which those scripts basically just configure, so they do now feel quite smooth.
Should note that this is still a manual process. For auto-tiling, you want e.g. Krohnkite.
The one you linked is only for KDE Plasma 5. For Plasma 6, you would use this fork: https://codeberg.org/anametologin/Krohnkite
I’m genuinely baffled how many oligarchs had contact with Epstein. I do believe their primary job qualification is a lack of morals, but there’s so many ways to be amoral, you don’t have to all be friends with the guy that offers pedophilia.
Yeah, I understand that it isn’t as bad, but it doesn’t explain why they didn’t go with something that’s entirely non-bad. We have the technology.
Yeah, one of the largest pieces of software humanity has created, next to Google Chrome and the Linux kernel, which are all around 30 million lines of code.
To give a frame of reference: With a team of 5 full-time devs at my dayjob, we can dish out a codebase of about 20 thousand lines over the course of two years.
A browser might be somewhat quicker to build, because the requirements are relatively clear at this point and you can start implementing many standards in parallel. But yeah, it’s still just an insane amount of code.
Well, the point is that GitHub is owned by Microsoft, so if they’re already developing an alternative to a Microsoft service, they would probably want to also use an alternative to a Microsoft service for their source code hosting.
We could start sending radio waves there and if something happens to be alive there, the response wouldn’t arrive until 300 years from now. 🫠
Oof, I was just talking about making things declarative there. If you want to configure it the old-fashioned way, like you would on other distros, then those difficulties don’t apply.
In more general terms, though, it’s a bit of a double-edged sword. The Nix package repository has more packages than other package managers: https://repology.org/repositories/graphs
So, the chance of finding an obscure software, that’s already packaged, is rather high.
Here’s the online package search, if you want to check the availability of some of the obscure software you use: https://search.nixos.org/packages
But then, yeah, the flipside is that, from what I understand, you can’t just download a random executable off of the internet and run it, because of the Filesystem Hierarchy Standard not being adhered to, as the post also mentions.
You can set up Flatpaks, and I believe AppImages would work, because those also live in their own FUSE filesystem. Well, and there is ways to emulate the FHS layout to get normal applications to run, too.
But yeah, way out of my field of expertise there. I have only one software installed which isn’t packaged for Nix, which is a program I wrote myself.
And to get sufficient FHS emulation for that, I just needed this line in my config:
programs.nix-ld.enable = true;
More complex programs will need a bit of extra configuration: https://wiki.nixos.org/wiki/Nix-ld
(I could also add a flake.nix file into my software’s repository, though, which would make it so it could be installed straight from my repo, as if it was packaged.)
I actually agree. This is my sneaky attempt at educating people about impl Deref. Although, I am still not sure how to feel about it, since I do actually see quite some similarities with inheritance…
Well, you’re in for a ride. The last half hour is the spiciest.
Screenshot the document, then paste it into a new document.
…I am just joking, I have no idea what they mean either. 🙃
Welp, I posted my hot take that impl Deref is similar to inheritance as a meme in !rust@lemmy.ml: https://lemmy.ml/post/42514248
Now, let’s see how many feathers get ruffled. 🙃
Oh wow, what the hell. I’m not actually familiar with C++ (just with Rust which gets similar reactions with the ampersands), but that’s insane that it just copies shit by default. I guess, it comes from a time when people mostly passed primitive data types around the place. But yeah, you won’t even notice that you’re copying everything, if it just does it automatically.
And by the way, Rust did come up with a third meaning for passing non-references: It transfers the ownership of the object, meaning no copy is made and instead, the object is not anymore allowed to be used in the scope that passed it on.
That’s true, except for data types which implement the Copy trait/interface, which is implemented mostly for primitive data types, which do then get treated like C++ apparently treats everything.
Yeah, I can understand the frustration. IMHO the Home-Manager way of doing things has some merits:
That last point is one that’s particularly relevant for me, because KDE Plasma’s configuration files are largely terrible. Home-Manager, together with Plasma-Manager, is the only sane way I know of, to automate the panel configuration in KDE.
But yeah, if you don’t use software with terrible configuration files, then I can certainly understand preferring dumb templating. I have also decided against using the Home-Manager-specific modules in places, or might only translate into the Home-Manager-specific module when I actually want to vary configuration values between two machines.
Just to give a quick impression of how terrible the KDE panel configuration is, this is a snippet out of the fittingly-called plasma-org.kde.plasma.desktop-appletsrc file:
[ActionPlugins][0]
MiddleButton;NoModifier=org.kde.paste
RightButton;NoModifier=org.kde.contextmenu
[ActionPlugins][1]
RightButton;NoModifier=org.kde.contextmenu
[Containments][1122]
activityId=f588743a-9bab-4f56-8f90-3616085ab6e0
formfactor=0
immutability=1
lastScreen=1
location=0
plugin=org.kde.plasma.folder
wallpaperplugin=org.kde.color
[Containments][1122][Wallpaper][org.kde.color][General]
Color=#79740e
Ah sorry, that doesn’t actually show any of the panel configuration, because KDE mixes configuration for the panel and desktop widgets and the Activities feature (like workspaces, but with separate wallpapers and widgets for each Activity) all into the same file.
So, here’s a snippet that actually shows the panel configuration, from just a few lines below the first snippet:
[Containments][1807]
activityId=
formfactor=3
immutability=1
lastScreen[$i]=0
location=5
plugin=org.kde.panel
wallpaperplugin=org.kde.image
[Containments][1807][Applets][1808]
immutability=1
plugin=org.kde.plasma.showActivityManager
[Containments][1807][Applets][1810]
immutability=1
plugin=org.kde.plasma.pager
[Containments][1807][Applets][1810][Configuration][General]
showOnlyCurrentScreen=true
showWindowIcons=true
wrapPage=true
[Containments][1807][Applets][1811]
immutability=1
plugin=org.kde.plasma.panelspacer
[Containments][1807][Applets][1812]
activityId=
formfactor=0
immutability=1
lastScreen=-1
location=0
plugin=org.kde.plasma.systemtray
popupHeight=432
popupWidth=432
wallpaperplugin=org.kde.image
What those numbers in e.g. [Containments][1807][Applets][1812] are? Ah, they just count those from 0 to infinity, whenever you add a widget through the UI.
And in case you were wondering since when INI allows for nesting section keys via [multiple][brackets]: It doesn’t. That’s a custom extension of the INI format, specifically in use by KDE.
Like, man, I love KDE for its features, but this is the stuff of nightmares.
Really my biggest frustration is that it isn’t transparent what’s generated and what’s not. If a human wrote the code, then I want to teach them, especially if there’s glaring logic issues in the code.
But at the same time, the most likely cause for glaring logic issues, is if they generated the code. And then it’s just a complete fucking waste of my time to try to teach them.