This is a gross article and doxxing this person is also gross and useless.

systemd will live rent-free in chuds heads and they will do nothing but use outdated and unmaintained software in protest.

Why are you posting Lunduke, a known alt-right fascist whose technical opinions are the culture war of the month, and not the original grant or better secondary sources?

• https://www.sovereign.tech/tech/arch-linux-package-management
• https://www.sovereign.tech/tech
• https://bbs.archlinux.org/viewtopic.php?id=311668

The STF regularly gives grants to various projects to focus on areas such as security and accessibility which maintainers often lack the necessary resources to focus on. The previous grant recipients include systemd, GNOME, OpenSSL, Curl, Pipewire among many others. This has been going on for a long time. Providing half a million euros to improve Arch Linux is not a backdoor scheme.

You should be ashamed of yourself for posting Lunduke, do better next time (or maybe do a simple 10 second background check of your sources next time).

Notice the most cracked developer “Arno” is a white guy with very expensive equipment who was raised in that environment for more than a decade?

CS not beating the white supremacy allegations any time soon in the West.

The level of smugness emanating from this meme is overwhelming, techbro levels of bad.

The wheel was never perfectly good actually, it was actually incredibly bad and needs to be fixed.

Keyboard -> Keyboard shortcuts from Settings will show all the available keyboard shortcuts. You can also create your own custom keybindings

These seem like a lot of personal design complaints rather than actual issues with GNOME itself.

And to my understanding Gnome expects you to use basically every application with a full screen window anyway

You misunderstood, that’s not what GNOME expects at all. Your app not maximizing on startup is because the app doesn’t maximize on startup. GNOME doesn’t have a setting to maximize all apps by default since that should be the app’s responsibility.

If you want the auto-tiling window manager experience, you’ll need to install an extension (Paperwm, tiling shell, Forge, Pop shell). Extensions are like applications, there’s no shame in using them.

NixOS’s installer has been seeing a lot of work, I’m not aware of the a11y changes but it has been getting a lot simpler and compact.

Both Debian and Ubuntu come with nonfree firmware blobs by default. Nonfree drivers such as the Nvidia proprietary driver can be installed graphically in Ubuntu if you open the drivers app.

Debian instructions are here and involves adding the non-free contrib repos to your /etc/apt/sources.list and then installing the nvidia-driver package

hyprland

A wayland compositor and tiling window manager. The lead developer of the project is a Polish transphobic workaholic.

why do ppl use the CLI for things like making and moving files? i find the GUI easier and faster as well as less prone to mistakes

If you understand how shell scripting works you can easily automate menial tasks. CLI is also an interface shared by all operating systems so if you know how to work around in a shell you’re not bound to any particular workflow/desktop GUI. Keep using GUIs though, they exist for a reason.

what is wayland and xorg, and why does everyone argue about them

Both are display protocols that are in charge of displaying graphics to your screen. Xorg is over 30 years old while wayland is only about 15 years old. The polemic about xorg was that the codebase was unmanageable and the design architecture of the program was inherently flawed (example: screenlocker getting access to your entire screen including apps and desktop, making writing malware for x11 a 3 line python script). X11 was designed during a time when people were using actual real life terminals and mainframes. Wayland is much more modern and akin to how modern graphics APIs are handled (for the most part)

Wayland at its core has and always will be design by committee so a lot of the arguing is necessary (though sometimes long-winded) to make sure to not repeat xorg’s mistakes. Protocols take months if not years to be merged into wayland and those protocols have to be implemented by wayland compositors themselves rather than sharing 1 program altogether like with xorg.

Watch this video for more information, explains it much better and is from an actual wayland board member.

Why YOU should write a Wayland compositor – Victoria Brekenfeld – HiP22 Berlin

matrix math acceleration hardware?

Can’t speak on that but if you want to get news about recent kernel developments (as well as hardware development) you should check out Phoronix.