All of these features are in KDE Plasma Dolphin.

Take a look the Dolphin settings and panels to enable these features.

The problem is not the lack of ideas, it is the programmers number and tech debt.

You can contribute to Dolphin KDE Plasma File Explorer: https://develop.kde.org/

Thank you! I didn’t try it! 😅

Let me share with you a talk: https://www.youtube.com/watch?v=1fZTOjd_bOQ

Them.

The taskbar is an outdated (30 years old) concept that should be extinct.

It was created to always allow the user to launch or resume their programs, even when they launch a fullscreen program.

I think it’s time to improve workflows. I don’t expect Microsoft leads the (proper) way. They are too busy including ads into the taskbar.

EDIT:

Let me share with you a talk: https://www.youtube.com/watch?v=1fZTOjd_bOQ

A question for the lemmy community: Why the negative votes? It is because the link is considered SPAM? It is because the TLDR of the post?

I always though that the votes is for the publication, not the referred content.

On the other hand:

• Loop-device exhaustion (slow, though Ubuntu has increased the limit via a patch).
• A single point of failure due to Canonical’s repository imposition (a closed garden).
• Unmaintained branches and snapped apps.
• Implicit installation of snapped apps through the apt CLI instead of the originally supported packages 🤬 (what the hell, Canonical!? Are you doing the same crap as Microsoft?).

The server-side closed garden is the opposite of an open ecosystem and the open-source community. You can add custom repositories to APT or Flatpak. Every new snap interaction feels like another step toward forcing the user to use it, instead of offering cool features that convince users on their own merits.

The last change (installing snapped apps when you run apt install) was horrendous. What’s next? Installing snapped apps when the user runs flatpak install?

Click-bait title. 👎 It’s a plugin for KWin. Here is the Pull Request, includes a video: https://github.com/taj-ny/kwin-effects-forceblur/pull/235

In the last Discover version, there is a warning; but distro developers can hide it (and they will, Canonical does not want a “Third-party programs could be dangerous for your system” disclaimer for their snap repository).

Source: snap So, tell it to Canonical (the company that develop Ubuntu). https://snapcraft.io/euruspro-desktop Report it.

Discover is a frontend client.

– Edit. I saw that you did it. 👍

You could try mine, SimpleK8s (kubeadm, containerd, systemd, buildroot), ~50Mb single file (kernel+initramfs). https://simplek8s.org/

The current footprint is lower than every alternatives commented on this article.

You are giving access to the docker socket (/var/run/docker.sock), so this container can create/edit/remove any container from your system, even add,edit, remove volumes or host path.

I have no idea if you can send modification API commands to a ReadOnly socket. I think you could, in the same way that you can do something with just HTTP-GET. Example: curl --unix-socket /var/run/docker.sock http:/images/json

Doc: https://docs.docker.com/reference/api/engine/version/v1.41/#tag/Container/operation/ContainerInspect

The node memory is not the same as the pod memory limits. Do you checkout your pods limits? kubectl describe pod blahblahblah

Doc: https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/

I prefer a simple style (just the folder icon, without the dolphin); but everyone have their own preferences. So… 🤷

As always, it can be customized for your own taste.

The article doesn’t comment the velocity: 16 T/s 🤷 You can see it in one of the article graph.

VC == Venture Capital

Good information here about EXO, and ChromeOS:

Neal Gompa (ニール・ゴンパ) 1 week ago

Is Exo going to continue to exist as a Wayland compositor? I figured it was going to be retired as ChromeOS turned into an Android overlay…

Fangzhou Ge 1 week ago

Yes, becoming Android overlay removes Chrome from the OS so Exo is going to retire. We still have to maintain Exo experience until the all ChromeOS device reach AUE or be updated to Android. Latest device AUE date I see are in 2033.

If folks don’t want Exo be listed we’ll just have Chromium here. Edited 1 week ago by Fangzhou Ge

Neal Gompa (ニール・ゴンパ) 1 week ago

I’m fine either way, if the Aura Shell is going to be around for a while, then it makes sense to include it.

I don’t even knowed that Chrome OS is/will be replaced by Android as an overlay.

Welcome. This is normal. It will be worst later (worst vision, worst reflex, laziness, etc). Just enjoy that your are alive and you will see new iterations (maybe HL3, someday) and new good games. You can not go back to your twenties or beyond, with all your over-the-top reflex, stress-free, free-time, and un-experienced view to be easy surprised. Just enjoy other things, other game types. Never play by obligation.

The first improvement (Media Foundation by FFMPEG) could be significant. Currently, VALVe generates large shaders to re-render those Media Foundation videos into other free codecs. These shaders can be several gigabytes in size for some games with lengthy videos. With FFMPEG, those videos could be played without being re-encoded as shaders.