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’d say we’re not there yet, but yeah, LLMs and image generators have accelerated it to the point, where I expect it to only take a few more years.
Gonna be interesting. There’s definitely going to be some enclaves, like invite-only places (in particular messengers), and potentially the fediverse won’t be worth targeting directly. But we do get lots of second-hand content here from places which are worth targeting, so yeah, will probably still notice the change here in one form or another.
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.
To be honest, it’s quite distributed for me, in the sense that I’m often just subscribed to a single person for a given instance. I have multiple subscriptions for these instances, though:
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.)
Welp, I posted my hot take that impl Deref is similar to inheritance as a meme in [email protected]: 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.
I guess, if you come from garbage-collected languages, you might be used to not needing the ampersands, because everything is automatically a reference in those…
I’ve only heard of them being trash so far. I was hoping they’d still have some resemblance of fun. But if the small fraction of folks who’ve upgraded to a Switch 2 actually were to play more than those on Switch 1, then that would be a pretty clear sign that it just isn’t fun on Switch 1.
But yeah, I’m not yet taking that for granted from this piece of news. I would assume, they wanted to drop the Switch 1 so quickly, because then they can start extending the game in ways that use more resources, which might be fine on their other supported platforms.
Ah yeah, via deref coercion, which is also called “auto-dereferencing” at times. Not to be confused with “auto-referencing”, which is also a thing[1].
You can do some wild shit with deref coercion. And when I say “wild”, I guess, I’m talking about the most normal thing for Java devs, because well, it’s a lot like inheritance. 😅
Basically, this concept of being able to pass &String into a parameter that takes &str also applies to the self parameter. Or in other words, methods implemented on str can also be called on String, as if String extends str.
And well, obviously you can also make use of that yourself, by writing your own wrapper type. You can even “override” existing methods in a sense by re-defining them in the wrapper type.
I had to play around a bit with it myself, so here’s a playground: https://play.rust-lang.org/?version=stable&mode=debug&edition=2024&gist=af65ed396dec88c8406163acaa1f8f8d
Damn, really makes it feel like they were waiting to drop that platform ASAP. I doubt, they have more players on Switch 2 at this point, well, unless the Switch 1 version is really terrible to play, I guess.
The rule of thumb I always tell people is that they should generally put owned data into struct fields and references into function parameters.
Seems like there’s now an option for that in Home-Manager: https://nix-community.github.io/home-manager/options.xhtml#opt-wayland.windowManager.sway.config.keybindings
But yeah, if you tried to use it when Sway wasn’t yet well-supported, or just want to use some obscure software in general, then yeah, things can get more complicated…
I mean, you don’t really need a fork for that. Anyone who’s motivated to actually improve the situation here, can just write appropriate documentation.
I guess, a fork would give you a new name, and therefore a clean slate where there’s not loads of contradicting information already out there. But yeah, that’s also a lot of work…
There’s all kinds of injuries or fatigue symptoms that may mean you can move your legs and sit, but you cannot stand…
I’ve heard the theory before that the collapse of cryptocurrencies was a larger factor, since you suddenly had lots of cheap GPUs on the market. If anything, I would guess that the pandemic slowed that down, because relatively many people got into gaming and we did have the chip shortage from factories being locked down…
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…)