I just discovered PaperWM a few weeks ago and I’m hooked. I can’t switch away from Gnome unless another tiling scrolling WM beats it. I hope someone makes a version of it for Cosmic.
I heard the wayland compositor niri is inspired by paperwm, fyi. Also I doubt that cosmic will be very extendable when it releases, since most components are rewritten in rust and compiled, thus unless they specifically add some sort of scripting support extensions wont happen as easily as on gnome
Even better: “#1 in the count y” with a damaged area right before the y. Missing letter or just bad kerning? No one will be able to tell until after they taste the pizza! 😜
The title of the video is actually “Plasma 6.1: the BEST LINUX DESKTOP (in my opinion)” and the video is not about argument what’s the best. It’s just regular coverage of the release. Just a little clickbait
I might be the minority, but I’m more inclined to click a video that says “Plasma 6.1: Release, features and my opinions” than one that proclaims it THE BEST THING (unless it’s from a creator I already know and like anyway, they get a pass as long as the content is good)
Yes, but YouTube is kind of shit these days with how it works for creators and quite often getting more views is a matter of setting clickbait title and thumbnail. He actually is one of the biggest Linux creators on yt
At least it's not one of those stupid "reaction face" thumbnails. A clickbait title is easy enough to parse as "not worth my time" but those punchable face thumbnails? Fuck me, the person that started that trend needs to find the nearest running belt sander and start licking.
Absolutely. I use gnome on all of my laptops and plasma on both of my desktops. End of story. Gnome is fantastic for touch screens and plasma is amazing for desktops.
Gnome is great for more than touch screens, it’s amazing with trackpads, and is extremely keyboard-focused. I’ve not really found a usecase where it doesn’t work well.
tell me if this is what I’m looking for. I build Lineage OS, which requires me to download a load of apps. I wish (analogy coming) I could manage everything like a npm project, where I can keep all the dependencies under a single dir. I want to use my package manager to handle the dependencies, rather than manually downloading the bins, mv-ing them to the dir, and setting the path. Once I’ve finished building, dispose everything with just one or two commands, leaving no footprint on my OS/machine.
I like it, though I’ve used it very little (just no need, ATM). They have some decent practice examples to go through, but it’s definitely a unique way of thinking about package management.
Nix has more packages , by far. Nix also automatically handles the dependent libraries for each package, which is something you can’t do with brew on immutable systems. This means that Nix can install software like espanso, which wouldn’t work on uBlue derivatives otherwise.
I really wish the uBlue maintainers would have opted for Nix over brew for that reason. It’s not much more difficult to do nix profile install nixpkgs#package-name over brew install package-name. They could have even aliased it to make it easier.
It’s faster than distrobox, it’s not within a box but on host, it’s easier than most package managers. I still go for flatpak first but for everything else I use nix. Especially for programming environment it looks to be much better than distrobox
Using containers on Linux has basically no performance loss compared to running on the host. They share a kernel and nothing needs to be virtualized (unlike containers on macOS and Windows), so anything you run in a container is basically the same performance as running it on the host.
I still agree though: using Nix is better than using Distrobox for many other reasons.
Sorry, faster because installing a package is faster than with other managers since you don’5 have to deal with any copr, debs or anything and it’s really fast on my install. I haven’t compared it directly but it feels very fast.
Nix is useful for CLI packages, which aren’t very simple to use through flatpak. It also has far more packages, and is very useful for creating development environments.
The ahayzen/silverblue-nix guide uses bind mounts from /var/lib/nix to /nix. The latter being created by making / temporarily writeable with chattr +i /.
It seems the Determinate Nix installer supports Fedora Atomic and SELinux.
On topic:
I really like Nix and home-manager. I’ve mostly switched to NixOS because it’s more convenient for window manager setups than building ublue images imo.
Having to mess with containers for different dev environments and keeping the up to date is imo more annoying than creating a shell.nix
Also being able manage my dorfiles with home-manager and installing software declaratively helps in keeping the system free of clutter.
Since no nix installer supported SELinux at the time, it was the only way to use nix on Fedora Atomic. With a better option available disabling SELinux is a bad idea indeed.
He thought it’s not possible to install nix on silverblue and another commenter tried to install it on secureblue. It’s not possible there. The problem is either somewhere along the supply chain (ublue) or with secure blue
I would love Slowroll or Leap, the tested packages of OpenSUSE using rpm-ostree. OpenSUSEs “immutable” model is worthless. It is not better than what Tumbleweed does with BTRFS snapshots
It’s better in one way, in that updates are applied on reboot rather than pulling the rug put from under running applications. But I agree that it doesn’t go all the way, as it doesn’t provide a verifiable base system with clearly separated modifications. OSTree would be great.
Another possibility would be to distribute a base image as a btrfs send stream (possibly differential against previous versions) containing a compose-fs image and associated files. And then OS extensions could be installed with systemd-sysext.
With users being bitten in recent days by this behavior when they were just expecting tmp files to be removed, systemd 256.1 is now available and does have a change to avoid inadvertently deleting your all-important home directory.
Thus those trying to do system maintenance without reading the man page could find their /home data deleted.
Initially the bug report was shot down by systemd developer Luca Boccassi of Microsoft with: So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”?
Maybe don’t just run random commands that you know nothing about, while ignoring what the documentation tells you?
Just a thought eh Ultimately though after much discussion the past few days, systemd-tmpfiles behavior is now improved upon.
Merged yesterday was this patch that now makes systemd-tmpfiles accept a configuration file when running purge.
The original article contains 289 words, the summary contains 155 words. Saved 46%. I’m a bot and I’m open source!
Doesn’t surprise me that a developer from Microsoft doesn’t understand this. To this day, when I select “Update and Shut Down” in Windows, it only actually shuts the computer down about half the time.
At this point, no. But it’s still incredibly annoying and a little spooky when I’m laying in bed and I see my computer screen light up in the next room when it’s not supposed to.
It’ll even wake itself from sleep when it wants to update, but it won’t start it automatically, I think because it hits the lock screen.
I’ll probably try Linux on ir when Windows 10 hits EOL.
Hey, it’s better than the gnome developers who will just close your issue when the discussion gets “too heated” or they refuse to see your use case as valid.
Wanting to and actually doing it are two different things.
The problem is that open source devs also have to be their own project managers, but those two jobs have very different skillsets.
In regular software development, it’s the PM’s job to deal with the drama, filter the idiocy out and collect concise and actionable user stories, and let the developers just write code.
In open source, you tend to deal with a lot of entitlement. All kinds of people, who never gave you a dime, come out out of the woodwork to yell at you over every little change. The bigger and farther reaching a project is, the more this happens, and it wears you down. I can only imagine what it’s like working on a huge project like GNOME.
And the toxicity feeds into itself. Be kurt with one person, and suddenly it gets out that you’re an asshole to users. Then people come in expecting hostility and react defensively to every little comment. And that puts you in the same mindset.
At the end of the day, you can’t satisfy everyone. Sometimes you gotta figure out how to tell someone their feature request is stupid and you’re not gonna work on it, especially not for free. And a lot of people need to learn to try to fix problems themselves before opening an issue. That’s kind of the whole point of open source.
Doesn’t have to be update and shutdown, I will click shutdown and it just reboots. Even disabled fast startup, so it’s not getting a wake event just as it’s hibernating.
Doesn’t surprise me that a developer from Microsoft doesn’t understand this. To this day, when I select “Update and Shut Down” in Windows, it only actually shuts the computer down about half the time.
There are some tasks that only can be done when the majority of the system is not in use. Windows prepares the files, reboots, does its thing in a preboot environment, then it actually shuts down.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.