Jure Repinc

Digital and software freedom/rights advocate from Slovenia, Europe. Also a member of the Pirate party. You can find me on Mastodon: @JRepin@mstdn.io

  • 230 Posts
  • 22 Comments
Joined 2 years ago
cake
Cake day: June 8th, 2023

help-circle






























  • Agree with this. Also they extensively use OpenQA CI and testing framework and it is what makes the rolling release openSUSE Tumbleweed the most stable rolling release distribution I have used since they can quickly catch an updated package that would cause problems and halt it being introduced. And even if something problematic would get through they really have excellent integration of BTRFS snapshoting with zypper and GRUB and system in general so you can easily boot from the last known working snapshot before the problematic update. And I would also say they have the best integration of KDE Plasma and KDE software of any distro out there. so yeah for these reasons I also consider openSUSE the bets GNU/Linux distribution out there.






  • Jure Repinc@lemmy.mltoGaming@lemmy.mlHDMI 2.1
    link
    fedilink
    English
    arrow-up
    33
    ·
    10 months ago

    Oh how I wish those TV manufacturers would get rid of HDMI and replace it with DisplyPort. HDMI mafia does not allow opensource implementations of HDMI specification and so not all latest features of it can be supported by graphics card drivers on GNU/Linux. Death to HDMI!



  • From my experince AMD drivers are pretty close, I’d even say slightly better on GNU/Linux, definitely more stable and consistent. For Nvidia, yeah they are bad at supporting GNU/Linux. Improved a lot through the years but still not there. For Intel, well not exactly an option for gaming, at least not the integrated GPUs I have used so far, but still better than in Windows in a similar way as in AMD case.

    P.S. Another great thing with libre/opensource GNU/Linux drivers: When you report a bug with Mesa3D drivers the bug is quite quickly fixed, especially when you can provide them with backtrace and/or Vulkan/OpenGL API trace. Doing a bisect of source code commits amd identifying the commit that introduced a regression also help a great deal. Good luck doing the same with closed/Windows drivers: you can wait for years and no fix.