• ByteOnBikes@slrpnk.net
    link
    fedilink
    arrow-up
    25
    ·
    9 days ago

    As a Linux user, I shit on Linux tutorials being obtuse because the solution is often like “then sudo [command]” and now run these 8 other commands. But at least with Linux commands, a smart person can piece together what’s going on.

    Windows, it’s even worse. It’s like a bunch of black boxes talking to other black boxes so after you right click to enable that property and add this registry key, you then have to reboot into your bios to turn on “Fuckboi” mode and take photos of your asshole for verification, then log into your Microsoft account to get this Powershell script and now you can finally see your children again.

    • JustARegularNerd@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      5
      ·
      9 days ago

      There is still not a neat replacement for wmic in PowerShell. If I want to do the equivalent of wmic product where name="some shitware" call uninstall it looks like this:

      $instance = Get-CimInstance win32_process -Filter "Name = 'powershell_ise.exe'" $instance | Invoke-CimMethod -MethodName 'Terminate'

      Like how the hell is that easier to understand Microsoft? Everything else in PowerShell follows a general pattern of Upper Camelcase.

      That’s just one instance of what I’ve found working with pwsh at work that leaves me thinking wtf

        • Matthew@midwest.social
          link
          fedilink
          English
          arrow-up
          2
          ·
          9 days ago

          I used to love batch as a kid. One time I was feeling devious so I wrote out a little script that deletes system32 and I emailed it to a classmate. I immediately burst into tears after hitting send and called her to let her know to delete the email.