161–170 of 233 posts
I wonder if the success of WSL this will risk making some tooling that is already less-than-stellar on windows (Git, for example) even worse when the group that actually has to work on windows proper shrinks.
Earlier quoted context omitted.
Good chance that your other VM software can't co-exist anyway. Many other technologies, Windows Defender among others, leverage virtualization through Hyper-V.
Hyper-V is not installed by default on Windows and I have not been required to install it for anything except WSL 2 (and Hyper-V itself). I think Docker on Windows also uses it but I don't use that. Windows Defender has never indicated a requirement for Hyper-V to me.
I must say WSL2 has genuinely been huge for me, to the point where I've finally been able to ditch macOS for a desktop with a Ryzen CPU. Honestly it's mindblowing how far Windows has come - if I were Apple I'd genuinely be scared of losing a large proportion of power-users as Windows becomes an increasingly viable platform for development.
I really like WSL. And Windows 10, well, it's not awful. I don't hate it anymore than I hate Mac OS's GUI. I find things especially nice with the new Windows Terminal. But the piece missing is still first class support for X (or Wayland) Linux applications. Without GUI Emacs, for example, or some way of integrating the Windows Emacs well, I find the WSL experience not as productive as booting into my actual Linux par…
Tramp[1] does this for Emacs. You can run Windows GUI Emacs and use SSH or another protocol to edit files and run commands within the WSL installation. It's pretty seamless.
[1] https://www.gnu.org/software/emacs/manual/html_node/tramp/in...
I must say WSL2 has genuinely been huge for me, to the point where I've finally been able to ditch macOS for a desktop with a Ryzen CPU. Honestly it's mindblowing how far Windows has come - if I were Apple I'd genuinely be scared of losing a large proportion of power-users as Windows becomes an increasingly viable platform for development.
Windows + Linux VM has been a better platform for a long time, even before WSL!
Microsoft recognized this and wanted to boost this workflow by providing it themselves.
> It’s still weird to say it, but Windows Terminal is hands-down the best terminal on Windows. Windows terminal is pretty good, but no, it's not yet the best terminal on windows. cmder is. It has panel split, quake mode, git integration... Now the read map of Windows Terminal is pretty convincing, so let's see how it plays out.
IMO, the best terminal on windows is a linux terminal running in WSL displaying to a windows x server. I use terminator and vcxsrv, and have not had any of the weird vim, ssh, tmux, etc rendering problems I had with cmder.
> there was a glimmer of hope that Web Development on Windows would be viable. I wonder if the success of WSL this will risk making some tooling that is already less-than-stellar on windows (Git, for example) even worse when the group that actually has to work on windows proper shrinks.
I expect the Windows Git will keep improving if they keep this Windows+Linux trend.
Just a reminder that enabling Hyper-V (needed for WSL2) will make your computer boot your current Windows install inside a VM too. This might makes a slight performance impact. And you might also encounter issues with Type 2 virtualization software such as VirtualBox or VMWare Workstation. (I will still stick to WSL 1 because of that).
For ML, 3D, games and what not is probably better to keep Linux in another kind of VM.
I must say WSL2 has genuinely been huge for me, to the point where I've finally been able to ditch macOS for a desktop with a Ryzen CPU. Honestly it's mindblowing how far Windows has come - if I were Apple I'd genuinely be scared of losing a large proportion of power-users as Windows becomes an increasingly viable platform for development.
Why use WSL2 instead of just running linux directly? Why do you need Windows in there?
Others prefer the Windows desktop, in particular for multi-screen.
Just a reminder that enabling Hyper-V (needed for WSL2) will make your computer boot your current Windows install inside a VM too. This might makes a slight performance impact. And you might also encounter issues with Type 2 virtualization software such as VirtualBox or VMWare Workstation. (I will still stick to WSL 1 because of that).
Earlier quoted context omitted.
You could already do that with WSL1. Source: I have Arch and Ubuntu on WSL1. Those didn't change. Other things did.
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.