• gornius@lemmy.world
      8·
      11 months ago

      Better in which way? WSL2 is a VM running ALONGSIDE Windows, not inside. Its performance is basically bare metal. If you have enough RAM, there is no reason to use cygwin instead of WSL2.

      • Possibly linux@lemmy.zipEnglish
        34·
        11 months ago

        In that case why don’t you just run a VM or install bare metal. WSL strips you of control just like Windows itself does.

        • Picture Pig@lemmy.worldOP
          1·
          11 months ago

          its complicated as i replied to someone else’s comment…

          im not a “it just works” user too but its complicated to explain why i use windows for now (but ill switich soon)

          like im totally a FOSS enthusiast but like…

    • azerial@lemmy.dbzer0.comEnglish
      5·
      11 months ago

      AHHHH “Has ptsd flashbacks from having to use Cygwin on a mixed build environment for a popular MMO that’s about some kind of war up in the stars…” lol NOT THE CYGDRIVE lol jk but it did take me back ~5 years.

    • QuaternionsRock@lemmy.world
      2·
      11 months ago

      Can Cygwin run Linux GUI programs effectively? What about GPU-bound workloads? Would happily switch if the answer to both of those is yes.

      • Possibly linux@lemmy.zipEnglish
        2·
        11 months ago

        You can run GUI apps but I’m not sure about GPU workloads. Wouldn’t bare metal be the best for that?

        • QuaternionsRock@lemmy.world
          2·
          11 months ago

          Wouldn’t bare metal be the best for that?

          Technically yes, but WSL2 is remarkably close to optimal in terms of throughput. Unlike WSL1 (a type 2 hypervisor), WSL2 requires Hyper-V (a type 1 hypervisor), meaning Windows also runs as a VM once it’s enabled. The Linux vGPU driver still needs to go through the Windows Nvidia driver as far as I know, but that is seldom the bottleneck for CUDA applications.