• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle

  • “This hardware works fine and even has compatible software that it works great with. But I’m going to prefer the broken software for other reasons. And that means it’s the hardware’s fault.”

    Software that is built to be compatible with a wide variety of hardware should be compatible with a wide variety of hardware.

    If software can’t handle a 16.5:16 aspect ratio, then that’s bad software. I don’t care how weird of a niche thing that is… just make your software abstract enough to handle those cases.

    It’s 2024, any resolution/aspect ratio/DPI combo should be supportable. There’s enough variety of monitors out there that we should have a solution for handling things on the fly without needing to have a predefined solution.


  • Should they? Yes. They should also be searching for previous bug reports. I’m sure a lot of people do. But if you have enough users, even if 1% of people don’t use good reporting behaviors, you wind up with a lot of duplicate or bad reports.

    There are plenty of blog posts out there that basically can be summarized as talking about how grueling open source work can be because users are often aggressive in their demands.

    But this is a prime example of debian “stable” doesn’t mean “no crashes” but instead it means “unchanging, which means any bugs and crashes will remain for the whole release”



  • Because the dev gets a huge number of bug reports for bugs that were resolved 5 versions ago.

    They actually asked debian to stop shipping the screensaver, because they were getting tired of saying “this is already fixed, debian is just not going to ship the fix for another year”. Debian didn’t want to stop, so the dev added the nag screen, because it was the only way to stop the flood of bug reports for things that were already fixed.