• 0 Posts
  • 38 Comments
Joined 2 years ago
cake
Cake day: June 22nd, 2023

help-circle


  • AdamBomb@lemmy.sdf.orgtolinuxmemes@lemmy.worldDaily Driving
    link
    fedilink
    English
    arrow-up
    2
    ·
    13 days ago

    Same. I recently spent a few hours failing to either build gamescope from source or get the flatpak versions of gamescope and steam working together. Others got it working a few months ago, but their steps didn’t work for me and I just decided I’d rather spend my time playing without HDR than keep trying at it. Wouldn’t have been so hard on a disto better supported by gamescope.
















  • I’ve been using Windows personally and professionally since 3.1, and Windows 11 was the last straw that finally got me to jump over to Linux for my home PC. I hate what Windows has become but I’ve got a lot of history with it. My experience with Linux (Mint FWIW) has been as smooth as it ever was in Windows, neither of which was perfect. I’m a definite convert from Windows and would encourage most people to consider taking the leap themselves.

    I gotta disagree with you about modern Powershell and terminals in Windows, though. Good terminal? Windows Terminal has been around for years now. It’s fast and functional. Whether Powershell’s parameters are “sane” is probably a matter of taste, but I’m definitely willing to stick up for its usability. Yes, the parameter names are much more verbose, but they all get tab completion out of the box, and you don’t have to type the full names at all, just enough of the start of the name to be unambiguous. For personal automation scripts, I think Powershell is way ahead of Bash. Parameters get bound automatically without needing to write for/case loops with getopts. You can write comments at the top of the file that automatically get integrated into Powershell’s help system. Sending objects through the standard pipeline means you spend a lot less time and code just parsing text.