![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
Look on phoronix for benchmarks. Plasma consumes less RAM and CPU than even XFCE.
Look on phoronix for benchmarks. Plasma consumes less RAM and CPU than even XFCE.
They should have code-named this release “Brooklyn”.
Awesome Keyboard with AI Support *
* On supported Operating Systems **
** With separate subscription.
There’s nothing wrong with UDP. At least not that I know of.
Sure, but the thing is: only a single person needs to break it temporarily in some way and this person can then leak the DRM free copy for everyone to consume.
That’s why DRM is such bullshit. It only ever punishes legitimate users. All others are unaffected.
For fileservers ZFS (and by extension btrfs) have a clear advantage. The main thing is, that you can relatively easily extend and section off storage pools. For ext4 you would need LVM to somewhat achieve something similar, but it’s still not as mighty as what ZFS (and btrfs) offer out of the box.
ZFS also has a lot of caching strategies specifically optimized for storage boxes. Means: it will eat your RAM, but become pretty fast. That’s not a trade-off you want on a desktop (or a multi purpose server), since you typically also need RAM for applications running. But on a NAS, that is completely fine. AFAIK TrueNAS defaults to ZFS. Synology uses btrfs by default. Proxmox runs on ZFS.
It likely has an edge. But I think on SSDs the advantage is negligible. Also games have the most performance critical stuff in-memory anyway so the only thing you could optimize is read performance when changing scenes.
Here are some comparisons: https://www.phoronix.com/news/Linux-5.14-File-Systems
But again … practically you can likely ignore the difference for desktop usage (also gaming). The workloads where it matters are typically on servers with high throughput where latencies accumulate quickly.
As with every software/product: they have different features.
ZFS is not really hip. It’s pretty old. But also pretty solid. Unfortunately it’s licensed in a way that is maybe incompatible with the GPL, so no one wants to take the risk of trying to get it into Linux. So in the Linux world it is always a third-party-addon. In the BSD or Solaris world though …
btrfs has similar goals as ZFS (more to that soon) but has been developed right inside the kernel all along, so it typically works out of the box. It has a bit of a complicated history with it’s stability/reliability from which it still suffers (the history, not the stability). Many/most people run it with zero problems, some will still cite problems they had in the past, some apparently also still have problems.
bcachefs is also looming around the corner and might tackle problems differently, bringing us all the nice features with less bugs (optimism, yay). But it’s an even younger FS than btrfs, so only time will tell.
ext4 is an iteration on ext3 on ext2. So it’s pretty fucking stable and heavily battle tested.
Now why even care? ZFS, btrfs and bcachefs are filesystems following the COW philisophy (copy on write), meaning you might lose a bit performance but win on reliability. It also allows easily enabling snapshots, which all three bring you out of the box. So you can basically say “mark the current state of the filesystem with tag/label/whatever ‘x’” and every subsequent changes (since they are copies) will not touch the old snapshots, allowing you to easily roll back a whole partition. (Of course that takes up space, but only incrementally.)
They also bring native support for different RAID levels making additional layers like mdadm unnecessary. In case of ZFS and bcachefs, you also have native encryption, making LUKS obsolete.
For typical desktop use: ext4 is totally fine. Snapshots are extremely convenient if something breaks and you can basically revert the changes back in a single command. They don’t replace a backup strategy, so in the end you should have some data security measures in place anyway.
*Edit: forgot a word.
I can still throw away my fire tv stick then. At the moment it still does the job I bought it for and I won’t produce unnecessary garbage for something that might happen in the future.
Remember that there were also big campaigns against tape recorders and VCR. They even managed to get VCR vendors to implement a feature that prevents users from skipping ads. So it’s not like it’s simply legal, the media corps were just not as successful in their lobbying as they are today.
You can btw “simply” opt out from this in the settings (look for “featured content” and disable it).
Yes it should be opt-in, but it’s not that hard to keep the fire tv (stick) being a good device for the price paid.
Shut up and take my
moneyprayers
npm? So this uses electron? I essentially run a stripped down browser to render a fucking OSD? I can’t do that with good conscience.
If only GeForceNow was available there. And Kodi.
Hopefully the regulation by the EU fixes this, then I am on board.
From what I understand, Nvidia may be right in this case and explicit sync seems to be the better approach.
There is a nice article on Collabora’s blog about it and it sounds plausible to me: https://www.collabora.com/news-and-blog/blog/2022/06/09/bridging-the-synchronization-gap-on-linux/
Just FYI, if you want to enable and start, you can use systemctl enable --now ...
.
I have an older InfinityBook and a slightly less older Pulse. What I hate about both is the noise. The fucking fans are so incredibly annoying. Also they are not just loud, they scale up in weird steps (not linear) making it seem like something’s attacking.
In consequence I use it with throttled CPU most of the time, but then even the desktop can become laggy.
Theoretically it’s nice hardware, practically I won’t get another.
That could help, but if a file is not shared that much (yet) or not many people are online at the moment, a single peer will still share many more parts, likely ending up with having shared significant amounts.
That is essentially how bittorrent works anyway. In Germany people lost in court over this. Also portions of a copyrighted file are a problem. If they can “proof” that they got a relevant portion (more than the typical fair use seconds) you are still on the hook.
All good, but I think it’s really often a misconception that a DE like KDE, which is big and brings tons of features, must be more ressource intensive than a (feature wise) smaller DE. Which, as the benchmarks show, is surprisingly not the case.