this post was submitted on 21 Jan 2024
202 points (94.7% liked)
linuxmemes
21291 readers
1514 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
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
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!
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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is kind of not really related, but last week, we've been onboarding two new devs into our programming project at work. Our team so far had exclusively used native Linux, while the two new folks were on Windows.
We recommended using a VM, because we had a recollection of how much pain programming on Windows was. Unfortunately, VirtualBox had performance problems on their machines and ordering a VMWare installation took a few days.
So, we spent those few days to see, if Windows was really still that much of a pain. They'd still need a VM for testing, but otherwise, our entire tooling should have been fine on Windows.
Fuck me, those days were wasted. One of our dependencies dynamically pulled in C code and compiled it, which you barely even noticed on Linux, but is apparently not a thing it can do on native Windows.
So, instead they were on WSL pretty early on, but that had all kinds of differences to a native Linux installation and they constantly had to fix the DNS config, because it kept being reset by Windows. In particular, while compiling Rust & C worked, it was extremely slow.
Eventually, they got VMWare and we started setting up the OS. We literally completed installing Linux before a compilation run had finished. And what had cost us multiple days to try to get going under Windows, was just working within an hour on Linux. And for some reason, compilation within the VM was about 20 times faster than under WSL.
I still assume, these are generally solvable problems and if our team had worked under WSL from the start, we would have had some of those solved.
But even taking that into account, there were just so many nonsense problems, which we never had to fix on Linux, that I'm still left absolutely baffled that some people genuinely use WSL for development.
I'm a C++ and Dart (yes I know unusual combo) dev on Windows
You feel my pain
My fucking god windows requires a whole month of just learning platform quirks and setting up a dev environment to START THE FUCKING WORK alone
Allegedly some new shite called dev drives and whatever are supposed to fix some of the disaster but I haven't tested it yet
Also ABSOLUTELY FUCK the entire C compiler installation and setup in Windows. My fucking god Microsoft had had 40 years to fix their tooling for THE most used language and you still need a dark ritual to make everything work and install MSVC and msys and clang
WSL's performance is drastically better when you don't save your files on Windows' filesystem.
Hmm, that would fit the pattern, as it sometimes also got stuck on just downloading things, even when the DNS config hadn't been reset.
Do you need to partition the disk then, to place ext4 or similar into a separate partition? I'm not sure, we can partition the disk in that corporate Windows setup our company uses...
Look up the difference between WSL1 and WSL2. If you're using 2 just make sure you're writing into /anything other than /mnt/driveletter, that should be ext4. For 1 it's directly mounted on the ntfs filesystem and you'll always have performance problems.
That is because windows filesystem is mounted to WSL through NFS and while transferring large files through that is ok, transferring huge amounts of small files is really slow.
Windows has dead slow file operations natively. Like orders of magnitude slower.
If they want windows just though windows in a VM in Virtual manager.