this post was submitted on 12 Nov 2024
529 points (97.1% liked)

linuxmemes

21281 readers
1166 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    529
    These people... (lemmy.world)
    submitted 3 days ago by trespasser69 to c/linuxmemes
    43 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] n3cr0 41 points 3 days ago (1 children)

    This is so true. Most of the tools justifying the use of WSL aren't even supported. Either because of technical limitations or because of security concerns.

    [–] HStone32 9 points 3 days ago (4 children)

    Why do people use wsl? The only reason I can think of is to take advantage of Bash and the shell environment. But if wsl runs in its own container separate from Windows, what's the point?

    [–] CheezyWeezle 13 points 3 days ago

    When WSL first came out, all the documentation i read from Microsoft led me to believe it was intended to help developers who are cross-developing software for both Linux and Windows to more easily test features and compatibility and to ensure software behaves consistently. It never seemed like they intended it to be used to run Linux programs fully and integrate into the Windows environment. It always seemed like it was just there for convenience so a smaller budget developer could develop on one machine and not need to be constantly rebooting or running VMs.

    [–] [email protected] 4 points 2 days ago

    Being a software developer but your work laptop is a Windows machine?

    [–] [email protected] 1 points 2 days ago

    Msys2 can be used for that btw

    [–] jacksilver 2 points 3 days ago

    Maybe I'm not aware of similar configurations you can do, but it's only sorta it's own container. VSCode can actually directly connect to it automatically so you can develop in host os but run directly against the container. Additionally this means some visualization/gui interfaces can be visible on the host side (this is a gift and a curse).

    So you basically have system integrated containers/vms. It's not perfect, but it is definitely leagues better than what windows development was prior and may have some advantages over Linux only deployments (not sure if the system integrations are feasible in Linux hosts).