Postgres never worked for example natively. Several npm modules would fail when running webpack.
wsl2 worked perfectly for these cases.
I wonder if people are mounting an ntfs volume in wsl2 which is really slow and janky?
Postgres never worked for example natively. Several npm modules would fail when running webpack.
wsl2 worked perfectly for these cases.
I wonder if people are mounting an ntfs volume in wsl2 which is really slow and janky?
We (postgres) did fix an ENOSYS (missing syscall) problem at some point so WSL could run Postgres. The surprising thing for me was how long it took for anyone to tell us it was broken/spewing warnings. That was forced when we changed a warning to a panic.
From reading the issue and related ones, it sounds like it might be related to some sort of unpredictable unclean VM shutdown.
> Postgres never worked for example natively.
That's a minor incovenience at worst.
I will stay put in WSL1. If I wished a VM I would have just installed VMWare and run some Linux ISO image from it.
I tried WSL because I thought it would be faster than a heavyweight VM. Turned out it's dog slow in comparison.
Honestly don't see a use for it.
I wasted a day trying to figure out if I had a problem with anti-virus or something that was blocking me before realizing that WSL I/O is just... well, slow.
People kept telling me to upgrade to WSL2 to solve that but the version of windows I had didn't allow it. Might have been a blessing in disguise given the data corruption bugs.
The root partition is slower, but I'm usually manipulating windows files anyway so both versions are similarly slow.
I use WSL2 right now, but only because I need to mount a vhd that's formatted with BTRFS.
The level of inconvenience purely depends on your stack and how its developed. Often things which don't bother me have huge effects on other members of my team, or on people working on other projects.
What a bizarre claim. It's irrelevant if you don't need Postgres, a minor inconvenience if you can easily adopt a workaround, and a show stopper if you were relying on accessing a local Postgres instance.