this post was submitted on 12 Nov 2024
547 points (96.9% liked)
linuxmemes
21612 readers
1394 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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?
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.
Being a software developer but your work laptop is a Windows machine?
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).
Msys2 can be used for that btw