![](/static/0b35d4a1/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/gWmVEUZ94Z.png)
What a based man. As a wise Spaniard once said, “Malditas sean las guerras y los canallas que las hacen”.
What a based man. As a wise Spaniard once said, “Malditas sean las guerras y los canallas que las hacen”.
The problem here is that we are dealing in largely imprecise terms. If we instead turn to semantic versioning for inspiring what we’d consider a large change, then Plasma 5 -> 6 is a big change, breaking previous API.
The new desktop edit effect is largely irrelevant under this rather precise terminology.
I don’t think anyone has misunderstood you here. You misunderstood what you wrote in your first comment. The new desktop edit window is not proposing any new functionality that wasn’t there, but showcasing it in a more streamlined fashion. That’s in itself refining the user experience, which is exactly what you wanted.
I tried it, but Firefox didn’t play some videos. As it turns out, it was an issue with non open source codecs. I’m not helping anyone navigate those issues, I’d rather point them out to a ready to go kind of distribution.
Wrong place, wrong time
Lutris? As far as I know, Wine doesn’t work on ARM. Unless they’re targeting x86 with mobile shape form.
According to tldr.chat:
Toolbx now supports the use of the proprietary NVIDIA driver in containers without the need to recreate them or use special options. This is achieved through the use of NVIDIA Container Toolkit to generate a Container Device Interface specification on the host, which is then shared with the Toolbx container’s entry point. The use of “nvidia-ctk” and “podman create” is not currently implemented due to root access requirements and the inability to update existing containers. The delay in enabling this support was due to the need for hardware access for testing, which was facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU.
Toolbx now supports proprietary NVIDIA driver in containers
NVIDIA Container Toolkit generates Container Device Interface specification on the host
Use of "nvidia-ctk" and "podman create" not implemented due to root access requirements and inability to update existing containers
Delay in enabling support was due to the need for hardware access for testing, facilitated by Red Hat providing a ThinkPad P72 laptop with a NVIDIA Quadro P600 GPU
Ah man, I was hoping I’d be rickrolled
checks version number
Every day is a good day to remember President Allende!
I’d argue that if you exactly call the model you refer to by their actual name, you’ll get much different reactions. For instance, expert systems have been around for a long while.
I think that Ready Player One was terribly ported from the book format to the movie. The book went so much more over the top than the movie did, the latter turning down on a lot of nerd aspects. Having said that, different formats need different ways for conveying the same idea. The main character would literally get a “+1 blazing sword” in the book. +1. As if it were an MMO or something.
Having said that, Dune (book and movie) were terrible. The movie felt plagued with references to stuff I didn’t get. Only recently did I read the book just to find it was as uninteresting as the movie.
I’ll never forget those opera singers singing right to my ears when a ship would land… Now that’s a way to startle a person.
On the bright side, reading the book has allowed me not see the second part of the movie.
Can you give ownership of it to someone else?
It feels to me that it’s looking to replace the Cut and Paste operations. This makes perfect sense for a tactile device, but I don’t feel like Dolphin is tactile ready - other KDE apps like Index intend to cover that ground instead.
Dolphin now includes a feature to move the selected items into a new folder, all at once
This one feels awkward
For me, it’s the Windows AMD application for using FSR and other stuff of my graphics card. I’m not willing to give up to 20 FPS on a lower end card.
Yup, that’s more like it. I hadn’t realized about the first paragraph.
deleted by creator
Isn’t that runner picked up by the KDE Application launcher as well?
Just to double check, are you sure you’re not running TempleOS?