I actually think 2024 has a very good chance of being the year of wayland, scene graph api just got finished wlroots side, wine is rapidly approaching ready for wayland, sway-side all that’s missing is global shortcuts and single window capture (and disabling vsync for games is about to be merged, if you care about that).
It’s all rapidly shaping up, they even fixed nightlight nvidia side. I think it all depends on nvidia fixing shit.
With GNOME and KDE going Wayland only, it is all but over for X. Qt, GTK, and Electron already work on Wayland so most apps are ready. Cinnamon, XFCE, Enlightenment, and MATE all have Wayland plans now. There are a few compositor libraries that other window managers and desktop environments can leverage.
NVIDIA is slowly getting their act together. Many of the legitimate complainants are being addressed. There are desirable features starting to appear that are Wayland only. Even non-Linux systems are adding Wayland support.
It is hard to believe after so many years but I think that, by Christmas 2024, most Linux users will have stopped using X and maybe even stopped talking about it.
This new entrant in the immutable space is not a replacement for ordinary Ubuntu
Not yet the replacement. It will be and I bet Canonical is targeting 26.04 LTS to do that. This is just the next step of trying to force all their users into Snap, just like when Flatpak was banned from being in by default of community-supported but official Ubuntu variants such as Xubuntu.
When you make a project with git, what you’re doing is essentially making a database to control a sequence of changes (or history) that build up your codebase. You can send this database to someone else (or in other words they can clone it), and they can make their own changes on top. If they want to send you changes back, they can send you “patches” to apply on your own database (or rather, your own history).
Note: everything here is decentralized. Everyone has the entire history, and they send history they want others to have. Now, this can be a hassle with many developers involved. You can imagine sending everyone patches, and them putting it into their own tree, and vice versa. It’s a pain for coordination. So in practice what ends up happening is we have a few (or often, one) repo that works as a source of truth. Everyone sends patches to that repo - and pulls down patches from that repo. That’s where code forges like GitHub come in. Their job is to control this source of truth repo, and essentially coordinate what patches are “officially” in the code.
In practice, even things like the Linux kernel have sources of truth. Linus’s tree is the “true” Linux, all the maintainers have their own tree that works as the source of truth for their own version of Linux (which they send changes back to Linus when ready), and so on. Your company might have their own repo for their internal project to send to the maintainers as well.
In practice that means everyone has a copy of the entire repo, but we designate one repo as the real one for the project at hand. This entire (somewhat convoluted mess) is just a way to decide - “where do I get my changes from”. Sending your changes to everyone doesn’t scale, so in practice we just choose who everyone coordinates with.
Git is completely decentralized (it’s just a database - and everyone has their own copy), but project development isn’t. Code forges like GitHub just represent that.
Well the bugtracker and additional features are not inside of the git repository. So they’d get lost. But each ‘git clone’ is a complete clone of the (source code) repository including all of the history of changes, the commit messages, dates and individual changes. That’s stored on every single computer that cloned the repository and you have a copy of everything locally. Though it might be out of date if you didn’t pull the latest changes. But apart from that it’s the same data that Github stores. You could just make it available somewhere else and continue.
I mean… Depends what you mean by 100% free firmware… If you mean only the boot firmware, that’s the case for PCs like the ThinkPads T400, T500, R500, W500, X200, as well as the Dell Latitude E6400. Note Libreboot even recommends the latter for new full libre buys, as it can be software-flashed without disassembly.
But if you mean 100% free including EC firmware, wireless firmware, and disk firmware, then this will probably never happen, or at least not until a very very long time.
What I’m trying to say is that it’s an uphill battle, arguably pointless too.
Before going with the current 30 series, I was using X200 and X60. They’re both good machines, don’t get me wrong. However, their age shows when trying to do modern tasks, even something as simple as web browsing.
The X60 doesn’t even have the hardware acceleration capability for my usual KDE setup. By the way, you’d be stuck with DDR2.
The X200 is much more capable than X60, but try to browse most modern sites and you’ll feel the machine getting hot. You could turn off javascript, but then you’ll be missing quite a bit of functionalities. I definitely wouldn’t run VSCodium on it for work. I’m currently using this one as a testbed for distrohopping.
To me, the 30 series is a sweet spot. The Ivy bridge is not too old for demanding computations of modern days. If you opt for the highest tier i7, you could beat a lot of the average ones from the following generations. If you don’t get the processor you want, you can always replace it since it’s socketed, at least for my W530, which should apply for T430 &T530 (not X230).
You might want to ask yourself: what are you trying to achieve, and more importantly, how can you measure what you’ve actually achieved? No, blindly following online articles is not a good measurement.
I found out later on that I had no way of actually verifying anything with libreboot. The build system is a pain in the neck to follow thru. I then tried doing it with coreboot upstream, and my experience building with it was much better. Even with it, I wouldn’t have the chance to look thru every line of code, I still need to just “trust” somebody.
You can definitely play around, but if that’s all you do, you’d be asking yourself why you did all that when you get bored.
Don’t like them, they are annoying to deal with - CLI naming is odd, files are stored unintuitively and if your whole system is not on flatpak, chances are the sizes are going to be absurd. One of the main reasons I wen’t with Arch is Pacman + AUR, never have to install a flatpak, because the package management is so good.
I don’t think the size thing is much of an issue these days outside of say IoT or very old computers. Absurd for say a single calculator app to be weighing like a gig or however much Gnome runtime is, but even in that situation it’s not much of an actual problem imo. And once you install anything else using that same runtime, you in a way halved the size of that app.
I always use Flatpaks when available, I have been using it for about 1~2 years and honestly, I haven’t found any issues that are deal breakers, mostly some missing storage permissions, but KDE makes this easy to deal with. I know some apps have some issues, but the biggest one that I had is that Steam Flatpak still requires Steam-Devices to be installed as a package, but that’s more to do with the way Steam Input works.
The only issue that I have is that uninstalling Flatpaks should present an option to delete the app data.
And does uninstalling a flatpak app also uninstall flatpak dependencies that came with it?
from what I have seen, NO it does not do so automatically. there is a flatpak command option to clean out unused runtimes, and another to remove user data.
delete app data after uninstalling?
you either manually delete the data, or there’s some flatpak command option, or you can use a tool such as warehouse which is available as a flatpak.
The Steam Deck is what got me to finally try modern KDE and eventually switch to it. I recently moved my gaming PC to Fedora 39, and considered trying Gnome again for variety’s sake until I remembered that it currently does not natively support VRR, so this is good news.
I think I prefer Plasma at this point, and I’m excited with Plasma 6 around the corner, but my desktop PC is basically a gaming appliance, so I think the relative simplicity of Gnome might be nice to run on there eventually as these features catch up. I like to have variety in what I’m running anyways. I appreciate that it gives me a wider perspective on my preferences.
Ahh, itsfoss.com. they had some article on “being a supercharged Joplin user” or some nonsense and suggestion 3 or 4 was “Create a notebook”… Really being a power user when you’re utilizing the most basic functionality the app was created for…
I thought about doing that but updating nixos confuses me. Does nixos-rebuild switch pull new packages? To my understanding there is a file that saves all currently installed versions of packages and switch only adds new things but wouldn’t update packages.
Like, if I want to update Google Chrome. Doing switch wouldn’t change anything if the config hasn’t changed, right?
I believe that’s correct – if nothing has changed from your last generation, then the new generation will be identical. But if something has changed, it will do a bunch of duplicating and remapping symlinks in the Nix store to ensure that everything plays nicely together and that you can rollback to a previous generation if needed.
So if you do a rebuild switch regularly, you will end up with gigs worth of old “copies” of things that aren’t being referenced in your current generation.
That’s what nix-collect-garbage handles – once you know your current generation is working well, you collect the garbage and recover that space, at the expense of not being able to roll back.
That’s why I think building a core system with NixOS and then having user software come from Flatpak is a nice combo for simple workstation that won’t update and bork itself, leaving my grandpa without a laptop until I can come take a look.
Edit: To clarify, nixos-rebuild-switch won’t update your Flatpaks at all – just the Flatpak service
That makes a lot of sense. I can setup their computer with nixos and stuff that needs to be updated regularly (like a web browser) can be flatpak which should be more stable too.
Then flatpak update would get them updated without rebuilding the whole OS.
My grandparents have been rocking Linux Mint for a few years. I have managed Chrome through Flatpak since I discovered that was possible on Mint. I’ve been flirting with the idea of having NixOS instead so I don’t have to remember what I’ve configured in the past. I’m not 100% sure now though :-P
Even Oracle, a company that funds OpenOffice and has its own proprietary fork of it, doesn’t use it internally. Oracle internal laptops come with libre office installed.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.