Readit News> This also sounds specific to GNOME, as mutter still doesn't have color management.
Gnome 49 should've solved that. [0]
[0] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4102
I don't think so. I'm on GNOME 49 and nothing has changed compared to 48.
I daily drive Ubuntu, the user experience is comparable (in many cases better) to Windows 11. The only sticking point for me is display drivers. HDR on Wayland is barely functional (in my experience), and getting things like hardware accelerated AV1 encoding, full Vulkan API support etc to work has been extremely difficult. Every time I login using a Wayland desktop, only my main monitor is detected and it defaults to 60hz. I have to go through a whole process of unplugging the "undetected" monitors and plugging them back in. X11 doesn't suffer from this, but of course does not support HDR.
Yes, this is almost entirely Nvidia's fault, and yes I should know better than to use NV graphics cards on Linux distros; but frankly, the barrier to entry should not be having to replace an expensive piece of hardware to achieve feature parity. (Obligatory "Nvidia, f*k you!")
> Every time I login using a Wayland desktop, only my main monitor is detected and it defaults to 60hz. I have to go through a whole process of unplugging the "undetected" monitors and plugging them back in.
Are you using GNOME? mutter has this problem where it does not retry commit on the next CRTC: https://gitlab.gnome.org/GNOME/mutter/-/issues/3833. If this is actually what's happening on your system, switching to KDE should solve it.
> HDR on Wayland is barely functional (in my experience)
This also sounds specific to GNOME, as mutter still doesn't have color management. You'll get a better HDR experience with KDE.
database64128 commented on Rust: A quest for performant, reliable software [video] youtube.com/watch?v=k_-6K... · Posted by u/raphlinus
This is demonstrably false. There are many approvers that do not work for Google.
Have you actually contributed to the Go standard library?
Yes, there are people who don't work for Google and can +2 on changes, but you still need 2 Google employees to at least +1 on your change before it can be submitted. This is mentioned in the Contribution Guide [0] and is enforced by Gerrit.
> Finally, to be submitted, a change must have the involvement of two Google employees, either as the uploader of the change or as a reviewer voting at least Code-Review +1. This requirement is for compliance and supply chain security reasons.
database64128 commented on Rust: A quest for performant, reliable software [video] youtube.com/watch?v=k_-6K... · Posted by u/raphlinus
Regarding Go, does Google actually "dominates“?
Google has a team for the development of the language but does that mean it dominates?
Yes. To land a change in the Go standard library, you'll need 2 Google employees to approve your change on their "trusted devices".
database64128 commented on Hitting Peak File IO Performance with Zig steelcake.com/blog/nvme-z... · Posted by u/ozgrakkurt
I see you use a hard-coded constant ALIGN = 512. Many NVMe drives actually allow you to raise the logical block size to 4096 by re-formatting (nvme-format(1)) the drive.
Since Windows 11 24H2, with the new color management feature turned on, I can get correct colors on the monitor in both SDR and HDR modes. So it ends up with HDR on at all times, and mpv can play HDR videos with no color or brightness issues.
GNOME, on the other hand, is stuck with sRGB output in SDR mode, so you get oversaturated colors. With HDR on, SDR content will no longer be oversaturated, but if you play HDR videos with mpv, the image looks darkened and wrong. I've tried setting target-peak and target-contrast to match the auto-detected values on Windows, but the video still looks off.