while(true){💩};

  • 1 Post
  • 73 Comments
Joined 2 years ago
cake
Cake day: June 11th, 2023

help-circle






  • Both are really good but it depends on your hardware setup and your goals.

    Do you have multiple monitors of different resolution and DPI mixes with a primary monitor thats 1440p or 4k at 90 to 144hz and/or variable refresh rate and older/cheaper side monitors that are 1080p 60hz? Wayland is going to be your best friend.

    Do you have a single monitor setup (or identical monitors) that you primarily program on or do system admin work that you need remote desktop from? X11 is gonna be your go-to (for the foreseeable future).

    Do you want to try exotic window managers like a sliding window manager? Wayland is the way to go.

    Wacom tablet? Wayland is working on it but its not quite there yet so X11 for you artists. This also lets you keep using color profiles until Wayland gets that implemented too (my bets are on Plasma getting it first).

    And so on.





  • It makes perfect sense if you’re a systems engineer.

    Downloading games costs bandwidth.

    Steam services millions of customers daily.

    Valve, correctly, decided to do a bit of load-balancing by prioritizing updates by how recently and frequently you play them, and spreads them out.

    This is nicer to their systems, and its nicer to most people who don’t live alone and have to share internet with other human beings in their home (or at work).

    You’d think it would be no big deal, bandwidth is “infinite” and “free” in most peoples minds. But there is a maximum throughput, and there is a cost in energy, time, performance, and money.

    Load-balancing, people. It saves lives.


  • Semperverus@lemmy.worldtolinuxmemes@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    25 days ago

    I do both. At home I do what you’re describing for Linux but at work I do sysadmin work.

    The stuff that winds up mattering on the Windows side tends to be a lot more social and resource based than it is hyper technical and digging in the weeds. If vendor software sucks, you debug it by yelling at the vendor to stop sucking (in the nicest way you can muster). You’ll need to document expected vs actual behavior but most of them will hop to and provide a fix fairly quickly. The rest is just making sure you have correct configurations and a proper environment set up (including security and such). Easier said than done of course.