• somebodythatIusedToknow@lemmy.world
    3·
    3 days 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
    34·
    5 days ago

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

  • wdx@feddit.org
    40·
    7 days ago

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

    Still better than cygwin

  • Blackmist@feddit.ukEnglish
    161·
    6 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.ukEnglish
        2·
        6 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
          4·
          6 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.worldEnglish
              3·
              6 days ago

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

          • Blackmist@feddit.ukEnglish
            31·
            6 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.

  • Hello Hotel@lemmy.worldEnglish
    6·
    5 days ago

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

    • x00z@lemmy.worldEnglish
      12·
      6 days ago

      Run Linux stuff on Windows.

      A big use case is development with Docker containers.

      • DigitalDilemma@lemmy.mlEnglish
        5·
        6 days ago

        Thanks - I can kind of see that, as docker on windows is majorly broken. I think I’d just run it in a linux vm, as I do with most of my developing, but I can see some might not want that overhead.

        • rmuk@feddit.ukEnglish
          7·
          6 days ago

          That’s the best bit about WSL (at least, version 2) is that it is a VM running a full version of Linux using Microsoft Hypervisor. There’s a bunch of drivers included that allow Windows and Linux to share filesystems and if you run Wayland/X apps in Linux they run on the Windows desktop.

          • DigitalDilemma@lemmy.mlEnglish
            3·
            6 days ago

            Sharing filesystems could be useful, I can see that.

            I do that with target dev platforms anyway, using things like NFS, samba and sftp, but I do see that it could work well for this.

    • forrcaho@lemmy.world
      10·
      6 days ago

      I only use Windows because I have to work with a corporation’s IT helpdesk staff to get on their VPN if I want to do contract work for them. They are not likely to help me get connected from Linux; they’ll just find another contract dev. Once in, I do everything in Linux because my code will ultimately run in a Linux cloud container of some sort. WSL works well enough for me to do this. I’d rather have Linux on bare metal, but whatever. I’m in; I’m coding; I’m getting paid. I’ll put up with a little bit of suck.

          • Hello Hotel@lemmy.worldEnglish
            2·
            5 days ago

            Oddly enoigh, they recognize this and are patching the hundreds of tiny holes. I would argue they began trying (IMO malformed) fixes back since the launch of windows 8 and .NET. It’s backwards compatability means tiptoing around some pretty huge tech dept. (Windows was DOS and had no security model at one point) Each time they try to pull people off of their older SDKs. If and when they dont stick, the pile of stuff to support grows one more.

            (Also WTH where they thinking with windows 8 apps!? The oversimplicity of the UI leading to huge patches of unused screen space, the art design or lack thereof, the janky unpolished UI elements. It’s embarrising for how much pride they had for it.)

    • Ricaz@lemmy.dbzer0.comEnglish
      4·
      5 days ago

      My company only allows us to use the company-provided Windows image, so I do all my work inside a WSL2 tmux session.

      JetBrains IDEs and VSCode also have WSL connectors so it works acceptably well.

      It also handily dodges all the Windows security policies (like installing software). You can even run Xorg apps from it.

      I’m still forced to use MS Teams and Outlook, though…

    • pool_spray_098@lemmy.world
      6·
      6 days ago

      I love having it at work, so I can write and run bash scripts on my Windows work PC.

      I have dozens if Linux servers available to me but sometimes it just is easier to run a script locally.

      • DigitalDilemma@lemmy.mlEnglish
        2·
        6 days ago

        I too do that, working from a windows vm and writing code for linux - but I push it to a linux vm for testing. Never occurred to me to use WSL and have another environment to configure and maintain for dev that’s different to the target one.

        But fair play if that suits you! Each to their own, and I’m sure I do things that make no sense to others.

    • wetbeardhairs@lemmy.dbzer0.com
      3·
      5 days ago

      Anecdote: I have an IDE that only works on Windows that can build applications for Linux. I use MinGW as part of the packaging process (AND I FUCKING HATE IT OH MY GOD. All of the pathing is broken!). As of yesterday I learned that WSL is a thing that might replace MinGW and make some processes of packaging for linux targets a little easier.

      • dejected_warp_core@lemmy.world
        1·
        5 days ago

        I’ve used both. What I can tell you is that moving to WSL is like moving to Linux wholesale. Treat it like porting your toolchain.

        IIRC, MinGW tools will happily take windows style paths (e.g. “C:\Users~myuser\projects”). If your tooling/scripting depends on being able to use Windows style paths, you’ll have to fix that first or you’re going to have a really bad time. There may be other small differences between MinGW tools and what ships on Ubuntu (or whatever Linux you decide to use in the WSL).

    • Torn Apart By Dogs@lemmy.blahaj.zoneEnglish
      2·
      5 days ago

      its for when the reqs include azure ad and the whole office has a m$ fetish yet you still gotta get your bag without losing your decades-built toolset AND you have a choice at all