Video decoding/encoding should work fine, better than Nvidia as fewer things support nvdec (the vaapi wrapper is enough though).

I have written apps in those toolkits. I can’t say it’s easier than the web of course but it’s not that bad.

Thats not relevant because Cosmic isn’t either.

My view is that if the goal was to effectively make good software they wouldn’t start from scratch.

If they used wlroots the desktop would be usable today with a good feature set.

If they used Qt or GTK they would have feature rich well supported software. (GTK4 could have been an improvement for them, it’s designed around being minimal and having platform libraries implement design choices)

They didn’t take a practical approach imo. You could argue its a long term investment but because of it it’s probably years off of feature parity. The only upside today is… it’s written in Rust.

The project is motivated by “I like Rust, lets make a whole desktop in it” not by good UX.

Fedora does not because they can’t support it. If a bug is found all they can do is shrug and point you at Nvidia. If they want to add a feature that breaks they would be stuck and have to hold back other drivers.

The kernel drivers were never an issue, but userspace drivers fixed this many years ago with glvnd.

It means it will break less on kernel updates. I don’t think it fundamentally changes much else for gaming.

Everything they do is open source, artificially holding back features doesn’t make sense.

Yeah, I don’t think that’s generally a problem. But modern firmware for some hardware is very complex and would be nice to be open.

It’s extremely easy to have a fully featured desktop that is open source software only.

Open hardware is hard though.

Some call that “source available” and not open source.

Also very unrelated, that’s about graphics apis like opengl.

https://www.khronos.org/opengl/wiki/Synchronization

Bit old, but I used a Windows Media Center remote, still see new ones for cheap. Then use lirc with an IR receiver.

That’s a totally unrelated part of the stack. These days you just have a compositor that combines the output of applications.

The model of out of process rendering in Xorg was done pre-2000s but GPUs became the norm and don’t work well this way.

deleted by creator

Every package has an architecture but you never have to care about it.

No its not, the package is literally “htop”.

I think you are mistaken. An example:

https://archlinux.org/packages/core/x86_64/glib2/
https://packages.fedoraproject.org/pkgs/glib2/glib2/

Debian:

https://packages.debian.org/bookworm/libglib2.0-0
https://packages.debian.org/bookworm/libglib2.0-cil

This is the common case, but Debian gets really out there some times.

And I’ll just say dnf is a much easier to use tool:

dnf install /usr/bin/aprogram
dnf install 'pkgconfig(glib-2.0)'

As a packager I’ll just say Debian is the one with the weird package names. Fedora just matches upstream names generally, similar to Arch.