this post was submitted on 21 Jan 2024
233 points (95.0% liked)

linuxmemes

26067 readers
312 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 users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • 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.
  • 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, no politics, no trolling or ragebaiting.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    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 remove France.

    founded 2 years ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Ephera@lemmy.ml 71 points 1 year ago (9 children)

    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.

    [–] Opisek@lemmy.world 25 points 1 year ago (4 children)

    WSL's performance is drastically better when you don't save your files on Windows' filesystem.

    [–] Ephera@lemmy.ml 5 points 1 year ago (1 children)

    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...

    [–] Exec@pawb.social 9 points 1 year ago

    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.

    load more comments (2 replies)
    load more comments (6 replies)