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

linuxmemes

21225 readers
111 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] Ephera@lemmy.ml 71 points 9 months 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 9 months ago (4 children)

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

    [–] gornius@lemmy.world 8 points 9 months ago (1 children)

    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.

    [–] Redjard@lemmy.dbzer0.com 5 points 9 months ago

    Windows has dead slow file operations natively. Like orders of magnitude slower.

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