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.

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.

Wow, that's amazing/terrible. Would you have a link to a repro?

I think this is the relevant bug: 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).

Thanks!

Thanks, this perfectly explains a weird error I have been seeing!

They didn't say that something changed.

But I'm intrigued, what did change?

WSL2 uses a VM while WSL1 uses a Linux like interface over a system-call DLL.

WSL2 sounds like a step back.

Their other choice was to make Windows file IO actually fast.

That just wasn't going to happen.

I/O performance characteristics changed, your ability to share the same filesystem for both OSes changed, etc.