Preferably the drivers and quirks of the hardware would all be patched upstream so that you don’t need to use a distro with the fixes patched in.

Mac Mini doesn’t come with a keyboard. So unless you’ve owned an iMac or bought a keyboard separately, you won’t have that convenience.

That being said, I haven’t touched the power button on my Mac Mini since I got mine on the 8th.

“Boiling The Ocean” refers to the fact that this is what all the hackfest topics share in common: They’re all very difficult long-term efforts that we expect to still be working on for years before they fully bear fruit. A second, mostly incidental, connotation is that the the ocean (and wider biosphere) are currently being boiled thanks to the climate crisis, and that much of our work has a degrowth or resilience angle (e.g. running on older devices or local-first).

https://blogs.gnome.org/tbernard/2024/10/05/boiling-the-ocean-hackfest/

I'm just saying that I think it would be more accurate to group Gnome closer to Windows and KDE than MacOS. Especially if Dash to Dock and Appindicators are enabled, like in Ubuntu.

I could switch between Gnome, KDE, Windows, and most Linux DEs relatively easily, but MacOS's feels quite different to me.

A good place to start is the "Water Cooler" section of the Fedora Discourse: https://discussion.fedoraproject.org/c/fun/8

I think a dev for Factorio discussed this issue on Brodie Robertson’s podcast.

Brand new Mac Mini, just came out today. It has a full year of warranty left.

My HDMI tops out at 144hz, issue still present.

1440p at 170Hz with the DisplayPort. But I also tried going down to 60hz, but in that brief time I did that, that made the flickering issue even more apparent.

I don’t get why this sort of picture always gets posted and upvoted when it’s wrong for most distros nowadays.

The TLDR is that Microsoft released a secure boot update that blocked insecure versions of GRUB. This update was only meant to go out to Windows users since releasing it to dual booted users could break GRUB. However, it was accidentally also released to dual-booted users.

The fix involves disabling dual boot, running a command to reset secure boot, then re-enabling.

Blender's Wayland support is not great because they're doing stuff from scratch. They're not using an existing toolkit like GTK, Qt, Electron, or even something like SDL to get Wayland support.

But if you're using an existing toolkit things are much easier and support is automatically there, you just need to do testing to ensure everything works.

The common biggest things that still use Xwayland are Chromium based apps and programs running under wine/proton. Chromium has an experimental Wayland mode that works well enough, but definitely has some bugs, especially around windowing. Wine Wayland is in the works.