• 1 Post
  • 829 Comments
Joined 3 years ago
cake
Cake day: July 7th, 2023

help-circle

  • And if you’re new to this world, my point stands exactly as you’re describing: you don’t buy hardware that is wildly incompatible with everything, and then complain when it doesn’t work. Which is what he’s doing here.

    Yes, I understand he’s familiar with this world through his FOSS efforts, and yes, I get that it worked under X11 (only the display server and not most apps at the time, but I digress), but my point still stands.

    The tone of the writing is an impatient “I’M STILL WAITING OVER HEEEERE”, and the response should be “Valid, but you’re going to continue waiting, so deal with it.” because UNLESS you intend to help contribute and fix the problem yourself, you’re at the whim of capacity of the project that is working on whatever features you need working. You’re getting it for free, not contributing, and still complaining.

    I find nothing more insufferable than people who do this exact same thing, and are extreme outliers to begin with. You know how many people have 8k monitors even to this day? Less than 1%, and I’ll wager that the vast majority of them don’t run in 8k resolution, because why? Literally nothing you’re going to touch - even in video production - is going to use it.











  • Anything immediately in the position after for is an assignment of whatever you put there as a temporary variable inside the loop. You can call it whatever you want. The “i” is just used a lot in examples in programming for “item” or “iterate”, but you can literally call it anything. Anything that refers to it later will have a single item from the list in $LIST assigned to it for each run through the loop.




  • No, it’s actually the opposite. He has an 8k monitor. Get rid of that, and then he has no blockers to using things the way he wants. Pretty simple solution.

    If you buy hardware that is wildly incompatible with almost everything, then there’s your problem. You don’t buy things knowing it’s incompatible, and then wait for compatibility to come around whilst complaining about it UNLESS you intend to buy it to put some effort into making it work on your own.

    That’s the entire point of this ecosystem and being able to upstream fixes.


  • It starts with the hardware first. You started well with tuning your CPU/MEM frequency settings, but that matters less if you’re running giant PSUs (or redundant), more drives than you need, and a huge number of peripherals.

    Get a cheap outlet monitor to see what your power draw is and track it at the wall. I just got these cheap Emporia ones. I’m sure there’s more reputable ones out there.

    Don’t go crazy with your networking solution if you don’t need them. PoE switches draw tons of power even when idle, and a 24-port switch is a huge draw if you’re only using 3 of them.

    Consider getting a power efficient NAS box for backend storage, and low power Minipc for frontend serving instead of using a power hungry machine for all your network apps.

    You can dive deeper into any angle thing, but these are the basics.


  • Dude…I’m not even eating my time with y’all who have zero clue as to how QA/CI/UAT works. It’s such a waste of time.

    Steam/Proton is only tested for KDE/GNOME, and that’s it. Hands down. Not even up for fucking debate. It’s a FACT.

    You can read the docs, repos, GitHub Issues, forums, and everything else you want. That’s the facts, and it’s not going to change. Just because it’s OSS doesn’t mean they have all the time in the world to make sure your edge cases work FFS.