I’ve been teaching Linux to a lot of high-school age kids this year. I picked Fedora Workstation for us to experiment with. It of course, uses GNOME. Like I mentioned in the above post I talked to them for 5-10 minutes about GNOME design and how it’s supposed to be used. One thing that surprised me is how much the younger generation found GNOME intuitive as soon as they learned to use the Super key. Many have spent more time on iOS than they have Windows. So some of the common pain points for us older folks, like not having a task bar, preferring each “App” to be full a screen and switching between them felt very natural for the kids. Very iOS like.

You can of course have your different opinion on if this is good or bad or if GNOME shouldn’t be the default on most distro.

Perhaps GNOME is a good default for distro because it’s similar to the interfaces young people are growing up with.

I’ve found GNOME a pleasure to use. From my experience many folks that use Linux like to tinker with their computers. Even those new to Linux see a world of possibilities. GNOME doesn’t really embrace this tinkerer philosophy. They have an opinion on what at desktop manager should be and they’re constantly working towards that vision.

When I introduce GNOME to new people I explain to them some the project goals, design elements and how it’s intended to be used. Then I tell them that GNOME is opinionated on how things should behave and look, and if you try to force GNOME to be something it’s not you’ll probably end up using poorly documented or unsupported third-party extensions that break things. Generally the advice is, GNOME is great, but not for everyone, take the time to learn the GNOME way of doing things and if you don’t like it you’re better off switching to another desktop environment than trying to change GNOME.

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.

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.

1. The installation process was easier than installing Arch (before Arch got an installer)
2. I don’t recall doing any regular updates after things were working except for when a new major release came out.
3. You needed to buy a modem to get online since none of the “winmodems” ever worked.
4. Dependency hell was real. When you were trying to install an RPM from Fresh Meat and then it would fail with all the missing libraries.
5. GNOME and KDE felt sincerely bloated. They seemed to always run painfully slow on modern computers. Moving a lot of people to Window Managers.
6. it was hard to have a good web browser. Before Firefox came out you struggled along with Netscape. I recall having to use a statically compiled ancient (even for the time) version of Netscape as that was the only thing available at the time for OpenBSD.
7. Configuring XFree86 (pre-cursor to X.org) was excruciating. I think I still have an old book that cautioned if you configured your refresh rates and monitor settings incorrectly your monitor could catch on fire.
8. As a follow on to the last statement. I once went about 6 months without any sort of GUI because I couldn’t get X working correctly.
9. Before PulseAudio you’d have to go into every application that used sound and pick from a giant drop down list of your current sound card drivers (ALSA and OSS) combined with whatever mixer you were using. You’d hope the combo you were using was supported.
10. Everyone cheered when you no longer had to fight to get flash working to get a decent web browsing experience.

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.

My ask here is for System76 to use a popular and shared tool by many Linux distributions to do firmware updates (fwupd) instead of rolling their own solution only installed by default on PopOS.

I’m not sure if a Dell still offers Linux support out of the box, but you can still easily install firmware updates on multiple Linux distributions using fwupd.

I’m going to piggyback off your comment to take a moment to complain about System76 computers, which I own and enjoy. That being said I wanted to run Fedora instead of PopOS.

It’s super frustrating to me that many of my old computers could automatically do firmware updates using fwupd, but to update System76 laptops I have to install from a copr repo their system firmware update service.

The funny thing is they do appear to support fwupd, I assume they just aren’t maintaining it.

A Linux laptop for Linux people, but they’ve managed to set it up where you don’t get the best experience unless you’re running PopOS. It’s little frustrations like this that make me want to go back to a Del laptop for my next computer.

Yeah! I’ve been doing the same. I actually find myself thinking “I haven’t participated in a conversation in over a week. I better find something to comment on.”

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 used to have a Shield. I donated it to GoodWill when Nvidia updated their UI to start showing ads on the Home Screen. I switched to Apple TV and not only does it not force me to watch ads, it’s actually just been a better overall. I haven’t had a single issue streaming anything from Plex to my Apple TV, where sometimes the Shield would struggle with high fidelity audio tracks.

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.