Hacker News new | ask | show | jobs
by pritambaral 3173 days ago
> easily mitigated by running Postgres (and MySQL and any other service you need) in the Windows layer.

Which comes with its own set of problems.

The entire point of MSFT in releasing WSL was so devs on Windows could use Unix-y goodness on Windows. I think that reasonably applies to the usage of Postgres too, and not just ruby/node/etc.

----

The proper way would be for Windows to autostart WSL when the user logs in / system starts, like providing a "Linux boot up" behaviour to the WSL userland and trigerring it on actual system boot up.

1 comments

> Which comes with its own set of problems.

Such as? Seriously, I'm running it like that and it works fine. I'll grant that Ruby on Windows only kind of works, but no problems with PG or MySQL.

I do agree though that WSL ought to run as a Windows service and do the normal Linux boot process when that starts.