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.

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.

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?