4 ms·

You could already do that with WSL1. Source: I have Arch and Ubuntu on WSL1. Those didn't change. Other things did.

• k__ 7y ago
  They didn't say that something changed. But I'm intrigued, what did change?
  • mehrdadn 6y ago
    I/O performance characteristics changed, your ability to share the same filesystem for both OSes changed, etc.
  • exdsq 6y ago
    WSL2 uses a VM while WSL1 uses a Linux like interface over a system-call DLL.
    • k__ 6y ago
      WSL2 sounds like a step back.
      • zlynx 6y ago
        Their other choice was to make Windows file IO actually fast. That just wasn't going to happen.
• akho 6y ago
  WSL1 managed to corrupt SQLite dbs. Which is really annoying, and does not happen with WSL2. My (casual, not work) use relies heavily on Nix, which is built around a centralized SQLite file. I did not enjoy that experience.
  • mehrdadn 6y ago
    Wow, that's amazing/terrible. Would you have a link to a repro?
    • akho 6y ago
      I think this is the relevant bug: https://github.com/Microsoft/WSL/issues/2395 https://github.com/Microsoft/WSL/issues/2395 WSL2 has been great so far (I’ve been using it for a few months now with no serious issues).
      • mehrdadn 6y ago
        Thanks!
  • petters 6y ago
    Thanks, this perfectly explains a weird error I have been seeing!
  • mahalol 6y ago
    Thanks for that, I have hit this bug once with WSL1 in the past and didn't think much of it at the time. Good to know what caused the issue.