Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Thursday November 24, @07:33AM   Printer-friendly
from the how-did-we-live-without-it dept.

The Windows Subsystem for Linux in the Microsoft Store is now generally available on Windows 10 and 11

Let the fantastical news be proclaimed that will cause cheers of joy to be heard across soylent land!

Today the Windows Subsystem for Linux (WSL) in the Microsoft Store is dropping its "Preview" label and becomes generally available with our latest release! We are also making the Store version of WSL the default for new users who run wsl --install and easily upgradeable by running wsl --update for existing users. Using the Store version of WSL allows you to get updates to WSL much faster compared to when it was a Windows component.

In response to the WSL community's requests, WSL in the Store will now also be available on Windows 10 in addition to Windows 11. So, Windows 10 users will also be able to enjoy all of the latest features for WSL including systemd and Linux GUI app support!

I notice there is not a wsl -remove option. I don't know what I would have done if they didn't include systemd support.


Original Submission

 
This discussion was created by janrinok (52) for logged-in users only. Log in and try again!
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2, Informative) by RamiK on Thursday November 24, @12:32PM (7 children)

    by RamiK (1813) on Thursday November 24, @12:32PM (#1281453)

    The real advantage of WSL2 (over, say, VirtualBox) is how developers can package user-facing linux apps that have convoluted linux dependencies as a simple .exe like container bundles: https://github.com/yuk7/wsldl [github.com]

    e.g. If you're developing a LaTeX editor, you can now release .exe packages that includes a whole customized distro with all the necessary latex packages and customizations without laying out 30 pages long installation manual. Like, in the most streamlined case, a user will just type "foobar latex editor" in the Microsoft Store search, hit Install, and end up with a Start Menu icon of your app that has access to the users' Documents folder under the File menu. And when users report bugs, you have a very controlled environment to deal with so you're not chasing some distro specific bugs anymore.

    Of course, development and run-time environments for specific stuff are also more convenient but developers generally end up needing the terminal anyhow so virtualbox images worked just as fine there too.

    --
    compiling...
    Starting Score:    1  point
    Moderation   0  
       Informative=1, Overrated=1, Total=2
    Extra 'Informative' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 3, Touché) by turgid on Thursday November 24, @12:47PM (2 children)

    by turgid (4318) Subscriber Badge on Thursday November 24, @12:47PM (#1281454) Journal

    How is this better than "sudo apt install foo" on something like Ubuntu?

    • (Score: 3, Disagree) by RamiK on Thursday November 24, @01:38PM (1 child)

      by RamiK (1813) on Thursday November 24, @01:38PM (#1281463)

      How is this better than "sudo apt install foo" on something like Ubuntu?

      What do you do if you need a specific version of a library that conflicts with whatever the user has? In NixOS we don't have that problem but the rest of the linux world is forced to hack around static builds, various containers like docker, AppImage, Snap, Flatpak, etc... with non-trivial deployment steps and all sorts of networking woes when trying to put together a local web-server or whatever. But in many cases I found myself spinning a VirtualBox instance to run a specific distro (typically arch) just to get some little thing running the way the developers has it running to overcome some minor issue... And sometimes, like with openwrt and specific latex projects, you HAVE to have this Debian or that Ubuntu version to get things running because the build environment is insanely convoluted.

      And that's coming from a linux user and developer pov. Now try delivering something to windows end users that needs such dependencies...

      --
      compiling...
      • (Score: 0) by Anonymous Coward on Friday November 25, @07:34AM

        by Anonymous Coward on Friday November 25, @07:34AM (#1281557)

        This is exactly my experience with Linux. The best advice is to use a stable LTS for the base system only for launching VMs.

  • (Score: 0) by Anonymous Coward on Thursday November 24, @02:59PM (1 child)

    by Anonymous Coward on Thursday November 24, @02:59PM (#1281486)

    I'm pretty ignorant of these newer technologies, but isn't what you described what Docker is, deliver a "container" with everything it needs in it?

    • (Score: 2) by RamiK on Thursday November 24, @07:32PM

      by RamiK (1813) on Thursday November 24, @07:32PM (#1281517)

      From a user's pov it's about the same. Though here you have a VM rather than a container under the hood and the developer can package their own host (windows) native software along with the vm in the .exe installer all configured appropriately so there isn't any configuration files editing and terminals command to execute. i.e. it's a (windows) user friendly solution.

      --
      compiling...
  • (Score: 2) by krishnoid on Thursday November 24, @06:32PM (1 child)

    by krishnoid (1156) on Thursday November 24, @06:32PM (#1281513)

    Along those lines, is LyX [lyx.org] available?

    • (Score: 3, Informative) by RamiK on Thursday November 24, @07:02PM

      by RamiK (1813) on Thursday November 24, @07:02PM (#1281514)

      Shouldn't be a problem since texlive and lyx are available in ubuntu so it will run as is. But the point I was trying to make that, if the lyx developer desired it, he could put together his own ubuntu vm with texlive and all the little tweaks and then put a wsl laucnher around that where users simply download the .exe installer and it all works just as well as it does in a native linux texlive ditro (unlike the many small breakages tex has on windows). He could even have the IDE run natively on windows and target the wsl's pdftex interpreter with a bit of scripting like jetbrains does: https://wsldl-pg.github.io/docs/Other-Software/jetbrains/ [github.io] https://www.jetbrains.com/help/pycharm/using-wsl-as-a-remote-interpreter.html [jetbrains.com]

      That would smooth out a few of visual issues that you probably get between the vm and the host.

      Regardless, it was just an example of what wsl2 does differently than virtualbox.

      --
      compiling...