In 2025, the package manager and frequency of updates are the only real differences between most distributions. I’ve been enjoying Flatpak for years now and hope it continues to build momentum. It offers the possibility of shared effort between distributions who depend on legions of volunteers constantly updating debs/rpms/whatever.
It feels like one of the last hurdles to eliminate so much of the duplicated effort associated with all these distributions.
I started using Linux right in the late 90’s. The small things I recall that might be amusing.
I really don’t agree with choosing to release with the UEFI bug they found. They describe it as cosmetic but those entries can last the lifetime of your computer, even if you wipe your hard drive. It’s bound to cause some confusion for years to come for Linux tinkerers.
I bought a new 2024 vehicle last year with a manual transmission. This will be the last manual I ever own. I don’t expect them to be around by the next time I get a car.
I’ve enjoyed driving stick since I was a teenager. It still makes my commute more enjoyable. A good rev matched downshift still makes me smile. I’m going to miss the experience when it finally comes to an end, but hopefully I can keep it up another 20 years.
I bought a new car with a manual transmission this year. It has a cool feature called “hill start assist”. Basically for the first 3 seconds I won’t roll backwards. It’s been nice.
I do this with my home network using FastMail. You can create App specific passwords for each service you add email notification support for. This means you don’t risk compromising your full accounts passwords. You can also put constraints on each app password, such as limiting it only to sending emails but not reading email or looking at your contacts and files. This is nice in case any of my passwords are leaked.
It was interesting reading your thoughts and all the different opinions in the comments. I enjoy firearms, and regularly go target shooting. I forget sometimes people don’t spend their time understanding firearms.
Yes, you are correct, the purpose of a firearm is to kill. That’s why they’re referred to as lethal weapons, where the word lethal can be defined as deadly.
It’s great you came to this conclusion on your own and it’s a great opportunity to explain some other aspects of firearms being lethal that folks often miss.
Since firearms are lethal weapons they’re not appropriate to use when less than lethal force is desired. This is why for example police “don’t just shoot criminals in the leg.” Because if they’re successful the person can still bleed out and if they miss they could accidentally apply lethal force to a bystander or the person they’re not trying to kill.
Another thing to understand is police should only have their weapon drawn if they fear for their lives or others. If the officer is following protocol, you shouldn’t see a firearm until the officer thinks lethal force is merited. Which is to say, if a cop pulls a gun, take it seriously.
I have a permit to conceal carry where I live. The laws understand firearms are deadly, and legally I can’t use or even draw my firearm unless I think my life is threatened or that I might suffer great bodily harm, think knife attacks or broken bones.
To add to that, because firearms are lethal, if someone flashes a gun in a threatening manner such as lifting up their shift to show the firearm in a holster during a heated argument, I could reasonably assume my life was in danger and legally respond with lethal force.
These are just some examples, but yes, guns are 100% designed to take life. You should always think of a firearm as a lethal weapon especially in situations where they’re pointed towards you.
Same, the builtin sync between devices using WebDAV was the critical feature for me choosing Joplin over Obsidian.
You mean like Wacom tablets? I’m curious to know what’s missing. I’ve been using one of those XP Pen tablets on GNOME and Wayland without much issue. I’m using it for writing more than drawing though.
I’ve been really enjoying Cockpit as well.
From what I recall the completely fair scheduler (CFS) used by default on most Linux systems has a lower average latency than the RT kernel. The RT kernel just gives you more consistency, hence the CFS having lower latency “on average”
So honestly for opening Firefox it’ll probably depends more on your SSD data rate, but in theory it’ll open faster on a “regular” distribution most of the time.
Real time is good for things like audio processing where having better guarantees that a process will get its share of the CPU is a benefit.
Hey man, I don’t want to discourage you, but this is one of those things where if you have to ask how to do something you’re probably not experienced enough to do it. That being said, as a learning opportunity even if you don’t make it far you’ll still learn a lot about how GPUs work.
I’d start by looking at any existing drivers you can find and see if you can document or find documentation for the commands fed to the GPU. From there you can look at the Mesa project for examples of converting Vulkan to instructions for specific processors and see if you can get it to all fit together for your project.
For newer APIs the kernels documentation is good:
https://www.kernel.org/doc/html/latest/
As for getting help, the #kernelnewbies channel on the OFTC IRC network is a good place to ask questions.
Have fun learning!
I’ve done some kernel development. I’d suggest using a modern system. Most of the basic stuff in the book is still accurate and there’s great documentation available to help find newer APIs. The kernel is always refactoring so learning to find newer info is part of the skills you’ll need to develop anyway.
I don’t think you really do anymore. I’d consider myself an experienced Linux user. I’ve been using it as a my desktop OS for over 20 years. I’ve also used Linux heavily through my career and am completely comfortable with the command line.
With recent installs of Fedora the only thing I use the command line for is the initial setup of the multimedia codecs. After that I haven’t been required to touch it.
I used to consider a terminal required to keep your desktop Linux system running. Now I look at is as an optional install for programmers.
That was a good read. I’d not really been sure of the differences between libadawaita and GTK were. It sounds like this frees up GTK to focus on being a cross platform GUI library, perhaps competing more directly with Qt. Meanwhile, libadawaita allows GNOME developers to keep leveraging GTK and tune it to their design guidelines.
I’ve only seen positive things come out of recent GNOME apps, but I wonder if the downside of GTK no longer embedding GNOME’s design language would be apps choosing to use GTK directly instead of libadawaita for better cross platform support. Will we end up with a less cohesive GNOME environment in the future?
I’m curious where you’re having issues. I’ve been able to use the little GNOME widget for setting up wireless connections for years.
Do you have an edge usecase that makes you drop back to using nmcli or is there a missing feature forcing you back to the ip/ifconfig commands?
No sarcasm, I’d just be interested in understanding your frustration a little better.
I recently purchased a laptop from System76. I’ve been very happy with it. You can get many of their models with coreboot used as the system firmware which is unique. I have been disappointed that they usually recommend installing open source, but not in-tree modules for getting things like keyboard backlight working. It feels a bit like they’re not a Linux laptop company but instead that they’re a Pop!_ OS laptop company.
Linux distributions have definitely standardized over the years. You get a kernel, systemd, network manager, Firefox, etc from basically every distro targeting desktops. Most will have different spins for the popular desktop environments as well.
From a purely technical perspective the main difference of distributions today is the package manager. Are you using pacman, apt, dnf, or something else? We know as users that while some of these different package managers have advantages and disadvantages they are all doing the same thing. You can get basically all the equivalent packages on each major distribution. I sometimes feel sad thinking about all the volunteer effort working in parallel, but not together to package the same software using different package managers. In many ways it’s duplicate effort that I wish could be spent in better ways.
Even package managers are beginning to converge. Flatpack is becoming extremely popular and is my current preferred way to add software to my system.
Leaving technicals behind the only major difference I see between distro today is their philosophy on how frequently to update and what to exclude. Does every package get a new update immediately when it’s rolled out upstream like Arch? Are we going to stick to older packages and only apply security/bug fix updates like Debian, or do something in between? Do we want to bend over backwards to make it easy to install Nvidia drivers or tell users we don’t support closed source software? Do we want to make it as easy as possible to install codecs or leave it to the wider community to figure that out on their own?
I don’t think there’s any right or wrong answer. Use what you enjoy!
Patience. Same things will work differently than you’re used to, and that can be frustrating.
Also be really sure to help true beginners understand software centers and package managers. I’ve been helping a lot of young people use Linux for the first time this year. Even though I mentioned it the first day and remind them frequently, if for example I ask them to install Java, half of them will download installers from Oracle’s website or wherever.