• somebodythatIusedToknow@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    8 hours ago

    WSL is actually worse than people think it is , I tried doing android via using wsl and wanted to run emulator , the amount of work you have to put and still the result you get is sub norminal. And this was in my job which made the matter even worse because my boss thought I was slacking .

  • dink@lemmy.world
    link
    fedilink
    arrow-up
    33
    ·
    2 days ago

    Most WSL users I know all run Linux at home; WSL is the best they can get at work.

  • Hello Hotel@lemmy.world
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    3 days ago

    WSL is Linux On a Budget. Its rough as hell but hey, if its all you have practical access to.

  • ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    95
    ·
    4 days ago

    When using WSL, be sure to not mention anything about that when reporting bugs because that’ll just confuse the issue for the maintainers. They like having that casually mentioned about 20 messages into the troubleshooting process.

    • DacoTaco@lemmy.world
      link
      fedilink
      arrow-up
      20
      ·
      4 days ago

      Pff, issue reports should ask for the output of ‘uname -ar’. It clearly shows its wsl as wsl runs a special kernel

    • chingadera@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      4 days ago

      I’m a big fan of going on WSL forums and letting them know everything is working well for give or take 20 messages, then I let them know I need help troubleshooting.

  • Blackmist@feddit.uk
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    1
    ·
    3 days ago

    I tried to get the *arr stack running on it at one point, using Docker.

    Do not do this. Just install the Windows apps. Yes, it’s a mess. Yes, they work.

      • Blackmist@feddit.uk
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 days ago

        It was a while ago now, bit I think it was trying to get all the individual bits to talk to each other (radarr to prowlarr, etc). I was following some guide and that’s where it all fell apart.

        • kamen@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          3 days ago

          Sounds like a network configuration issue of the containers - you either have to use the host network (probably not recommended) or to map the necessary ports of each app. But trying to do that in WSL sounds like an extra layer of fuckery that you don’t necessarily have to deal with. Running Docker directly on Windows sounds like the more sane thing to do in that case.

            • kamen@lemmy.world
              link
              fedilink
              English
              arrow-up
              3
              ·
              3 days ago

              I know, but it’s managed by Docker, i.e. you don’t have to do anything special.

          • Blackmist@feddit.uk
            link
            fedilink
            English
            arrow-up
            3
            arrow-down
            1
            ·
            3 days ago

            Yeah, it was blocking the networking between them, and after Google failed me for an hour, I realised they all had Windows installers so there wasn’t really a lot of point persevering with weird half-broken versions of Linux and Docker.

  • foggy@lemmy.world
    link
    fedilink
    arrow-up
    46
    ·
    edit-2
    4 days ago

    I don’t think anyone is a “wsl user” so much as they’ve found themselves in a position where the lowest friction solution is utilizing wsl for a given situation.

    Around 2019, even up until like 2022 if you wanted to run docker in windows, that was how to do it.

    • coconut@programming.dev
      link
      fedilink
      English
      arrow-up
      21
      ·
      4 days ago

      I learned the shell in wsl before I switched to Linux full time. I wasn’t trying to learn it intentionally. Just didn’t want to develop software on windows. It’s a great gateway drug that reduces friction by a lot.

    • frezik@midwest.social
      link
      fedilink
      arrow-up
      7
      ·
      3 days ago

      That’s where I was a few years ago, and then I switched back to proper Linux. I was only keeping Windows at all for games, but then most of the games I played started working fine on Linux (thank you, Valve).

      Plus, I tried doing some TensorFlow stuff with CUDA (Nvidia) GPU acceleration. In theory, you can do it in pure Windows, but nobody has bothered trying to do that. You’re on your own if you try it. The usual way is to do GPU passthrough to WSL. There have been three different ways to do that over the years, only one of which currently works. If you happen to Google a page that tells you one of the wrong ways, there’s a good chance you’ll need to reinstall to get it working the right way.

      Using pure Linux for this stuff is no problem. Just use Nvidia’s server drivers instead of gaming drivers. All the AI datacenters are using Nvidia GPUs on Linux, so Nvidia is highly motivated to make this work. Someday, Windows might be as easy to use as Linux.

    • folkrav@lemmy.ca
      link
      fedilink
      arrow-up
      8
      ·
      4 days ago

      Pretty much my situation. Work stuff, Windows machine, but Linux/Docker workflow and I refuse to let go of my POSIX shell.

    • Narwhalrus@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      4 days ago

      What’s the current best way to run docker on Windows?

      I’m still using wsl(2) for that in 2025 because it seems to be the path of least resistance on Win11.

      • foggy@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        4 days ago

        That could very well be the best practice. I haven’t had to run docker in windows since then.

  • wdx@feddit.org
    link
    fedilink
    arrow-up
    31
    ·
    4 days ago

    Me looking disgusted at myself in the mirror, for I am doomed towards eternal Microsoft-dependency at work.

    Still better than cygwin