The Windows Subsystem for Linux is now open source
blogs.windows.com
Today we’re very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo:

Today we’re very excited to announce the open-source release of the Windows Subsystem for Linux. This is the result of a multiyear effort to prepare for this, and a great closure to the first ever issue raised on the Microsoft/WSL repo:

https://github.com/microsoft/WSL

  • JuryNow@lemmy.worldEnglish
    0·
    3 days ago

    Making WSL open source could actually lead to some useful contributions and better transparency overall ; and good for Linux tools?

  • yarr@feddit.nlEnglish
    0·
    3 days ago

    Great! With this source code out, I can finally complete the port to Linux. I call it WSL24L, aka “Windows Subsystem For Linux 2, For Linux”

    • steeznson@lemmy.worldEnglish
      0·
      3 days ago

      Do you name every FOSS project? This is uncannily close to what an actual open source project would be called, including the logic behind it.

      • 0ops@lemm.eeEnglish
        0·
        2 days ago

        Nah, needs more recursion. The ‘W’ in “WSL” stands for “WSL”

  • MehBlah@lemmy.worldEnglish
    0·
    3 days ago

    Garbage on top of garbage. The true nature of macroshafts desperate grasp to get control of linux.

    • Womble@lemmy.worldEnglish
      0·
      3 days ago

      Its a godsend when you have to use Windows for whatever reason and you can have a functional OS to do things with.

  • Kazel@lemmy.dbzer0.comEnglish
    0·
    3 days ago

    fuck microsoft and windows so hard. had to reinstall that shitshow on my mothers computer because a driver update fucked the whole networkstack… they throw error codes and what not but give no help whatsoever. the conclusion of everyone for every problem is to reinstall windows… shitshow of an os, keep your dirty hands of linux!! can’t wait to nuke it and install linux there and have no windows machine left

    • FreedomAdvocate@lemmy.net.auEnglish
      0·
      3 days ago

      If you’re having to reinstall windows regularly you’re not very good at being the tech guy. I say this as someone who manages a support team for 50+ Windows machines, and who has been the tech guy for all my friends and family for decades. I can count the number of times I had to reinstall windows on one hand, with a few fingers to spare.

      • Kazel@lemmy.dbzer0.comEnglish
        0·
        1 day ago

        If you’re having to reinstall windows regularly

        says who? what’s the fix for code 56? what can i do in the registry do solve the botched update? which files to check and/or remove? logfiles that give me a clue? come on tech guy enlighten us

        • FreedomAdvocate@lemmy.net.auEnglish
          0·
          11 hours ago

          Strange cause like I said, I’ve been doing this for literal decades and can count the number of times I’ve had to reinstall windows on one hand, with a few fingers to spare. 50+ windows machines at any given time at work for 15+ years. Every family members computers for 25+ years.

          One hand.

          With fingers to spare.

  • stebator@lemmy.worldEnglish
    0·
    3 days ago

    This is for WSL2, not for WSL1. WSL2 is just a VM, not a big deal it it’s open-sourced. WSL1 is superior to WSL2 in every way. BTW, WSL2 is not a continuation of WSL1, they are being developed in parallel. I still try to use WSL1 whenever possible. For Linux specific features, like systemd dependancy and mounting file systems, I’d use full-featured VM instead of WSL2.

    • JackbyDev@programming.devEnglish
      0·
      3 days ago

      I thought WSL2 had a few specific advantages over WSL1, something about disk writes and/or Docker? But yeah, WSL1 was such a cool concept. My understanding is they implemented all the syscalls and API in it so it’s basically native.

      I tried to use them, as I do most tools like that. On Windows I have always stuck with the MSYS environment that Git for Windows gives you. It’s easy enough to work with and has most everything I care about. Plus it’s easy to set up. With wsl it’s more like a separate thing, it wasn’t as easy to run in place. A lot of times I still used batch or powershell scripts so it wasn’t totally bash. Like Docker is easier to use from not bash in Windows because the syntax is so wonky.

      But now I don’t use Windows at all.

      • baduhai@sopuli.xyzEnglish
        0·
        2 days ago

        I’ve recently started using windows again for work, after not touching it for like 15 years, msys2 makes it tolerable.

        I’m a devops engineer, and my company won’t allow me to use WSL. Go figure.

        • KeenFlame@feddit.nuEnglish
          0·
          1 day ago

          Uh… But that’s what it’s for? Like it’s it’s primary purpose…? They created it for devops…? What are they smoking?

          • baduhai@sopuli.xyzEnglish
            0·
            1 day ago

            Msys2 was not created for devops, I just happen to be a devops engineer who uses it. Their websites describes it as:

            MSYS2 is a collection of tools and libraries providing you with an easy-to-use environment for building, installing and running native Windows software.

            Because it makes software building, packaging and distributing as simple aand standardised as it is on Linux, it means they effectively have a very good CLI on their hands. On my work laptop, I now use WezTerm with fish shell and helix editor for my workflow, and live in the terminal. Would this be possible to do without msys2 or wsl? Yes, but it would be a huge pain.

        • JackbyDev@programming.devEnglish
          0·
          2 days ago

          MSYS2 is odd, I could never figure out how to set it up a sort from the one with Git. When I was more of a power user I used Cygwin. Babun is cool but unmaintained last I remember, and is just Cygwin with some enhancements.

          As much shit as MS gets (and rightfully so) around 2019 they began turning their reputation around for dev stuff. They’ve lost all that good will though.

          • baduhai@sopuli.xyzEnglish
            0·
            2 days ago

            I could never figure out how to set it up a sort from the one with Git.

            That’s because the one provided with git is a nerfed version of msys2. If you install msys2 as a standalone thing from their website, you get everything you need for a functional CLI on windows. Most importantly, you get a real package manager and decently populated repositories.

    • JustARaccoon@lemmy.worldEnglish
      0·
      3 days ago

      Means that now anyone can fork the project and make changes or iterate on it without needing to wait for Microsoft to fix things.

        • JustARaccoon@lemmy.worldEnglish
          0·
          3 days ago

          Np! Also forgot to add, I haven’t checked the license but generally with proper open source projects (as in not just source available) it means that even if Microsoft tries to revert this at any point, having forks of this version and continuing to develop and distribute versions of it is A-OK

  • Gumus@lemmy.worldEnglish
    0·
    3 days ago

    I know there’s a lot of hate for Microsoft on Lemmy, but WSL is one of the best parts of Windows. It’s really powerful and well integrated to Windows. Since I still can’t leave for pure Linux install, I’m glad for WSL.

    • I'm Hiding 🇦🇺@aussie.zoneEnglish
      0·
      3 days ago

      The only Windows PC I use is my work computer.

      GPO blocked WSL.

      I can’t even escape to a command line with the right flavour of slashes between directories. For eight hours a day, all hope is lost.

    • lepinkainen@lemmy.worldEnglish
      0·
      3 days ago

      WSL made windows tolerable in the time I had to use a windows machine for work.

      macOS is still the better choice for corp approved work, integrates decently with IT systems and is a “real” unix system underneath.

      Linux on a corporate desktop is mostly about how well you know the IT guys and do they trust you. And of course the software stack.

      • cmhe@lemmy.worldEnglish
        0·
        3 days ago

        Linux on a corporate desktop is mostly about how well you know the IT guys and do they trust you. And of course the software stack.

        I would say it depends more on the commitment of the IT admins to support and manage a fleet of Linux workstations. There are Linux “Active Directory” servers, configuration provisioning tools, ways to centrally and automatically rollout updates, etc. It really depends on if the IT guys invest the same amount of effort to support them or not.

        • lepinkainen@lemmy.worldEnglish
          0·
          3 days ago

          2000 people, 3k+ devices and one dude wants a Linux laptop.

          Not happening 😀

          But it did work in a smaller company of around 30 people, mostly because the IT guy was a Linux user too

      • interdimensionalmeme@lemmy.mlEnglish
        0·
        3 days ago

        IT just said no for WSL “ask your manager”

        My manager barely knows how to read his email

        and doesn’t understand why I want 3rd screen

  • mvirts@lemmy.worldEnglish
    0·
    3 days ago

    I am legit excited to install WINE Subsystem for Linux

    Or how about KDE on ReactOS on WSL?

    The possibilities are endless