• 12 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: July 25th, 2023

help-circle










  • Blender and DaVinci Resolve work better on Nvidia. AMD might work, but it will be a hassle and you’ll likely need the proprietary AMD drivers anyway.

    With Nvidia supporting Wayland and the open-source NVK continuing to get better, you could even switch to open source drivers for gaming at some point, if you prefer.

    Edit: I’ve had enough issues with AMD GPU’s clocking down while gaming, leading to micro stuttering. So don’t buy AMD just because everyone tells you they work flawlessly.

    For CPU and mainboard, everything works well — just don’t buy a random unknown SSD from Amazon, then you’re asking for data loss and random issues.






  • I believe the advantage is that old drivers still work as they are all in the kernel. With them sharing much code it’s not even that big of a disk space issue. Edit: A more dynamic approach would be great though, especially with this size issue popping up.

    In a way it’s great that I’m able to replace any part of my system and it just works without me having to make sure the old GPU driver doesn’t leave some traces behind–altough while writing this the latter part shouldn’t be an issue with Windows auto download and installation of drivers.



  • Creating a wayland compositor based in wlroots is much more work than an X11 window manager. And then there’s quite a bit of work to keep up with new Wayland protocols.

    But I personally don’t think there’s a need for more compositors, since the existing compositors do support all kinds of tiling.

    E.g. river has custom layout providers, which allows for creating completely custom tiling behaviour. There’s even a hyprland plugin which implements river-layout-v3.