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.
Also new people are still motivated to change stuff. They are not yet worn down by bureaucracy.
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.
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.
One problem is that they need to put a price tag and therefore a timeline on such a project. Due to the complexity and the many unknown unknowns in theses decades worth of accumulated technical debts, no one can properly estimate that. And so these projects never get off and typically die during planning/evaluation when both numbers (cost and time) climb higher and higher the longer people think about it.
IMO a solution would be to do it iteratively with a small team and just finish whenever. Upside: you have people who know the system inside-out at hand all the time should something come up. Downside of course is that you have effectively no meaningful reporting on when this thing is finished.
It only needs to work long enough for the current management to cash in on their savings. Then it’s their successors problem.
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.
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.
As a kid another kid regularly bullied me. Nothing extremely serious… pushing me, grabbing me, putting me in a headlock, stuff like that whenever he felt like it and/or wanted something. Parents and teachers were not able to stop it and I basically just got retaliation. One day when he came at me I simply kicked and managed to hit right in his balls. He ran away crying. Never bothered me again afterwards. Still feels good.
For nougat, the Milka stuff is better. If you want real chocolate, take Caotina.
I would love to upgrade to one, but from tests I gathered that they have an exceedingly bad idle power draw. Given that the card would idle most of the time, I don’t really want to waste power on it if nvidia and amd manage to stay far lower.
Why though? I daily-drive it on multiple machines. The native encryption and ZFSBootMenu make it an awesome root fs. And incredibly easy to use with the way it handles mount points.
You can easily turn it into a “pubic display” once it’s set up.
I have a few projects where parts are Java, parts are Go and parts are C. Having that in a single workspace can be convenient.
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.