151–160 of 233 posts
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.
No free lunch, of course. Faster file access with WSL2 (vs WSL1), if you stay in the Linux world. But if you point it at Windows files (/mnt/c, etc), it's pretty slow. WSL2 just moved the slowness from one side to the other. Accessing the Linux FS from Windows (\\wsl$\) is also slow. That said, I am a fan, and get a lot of use out of WSL1. Since I don't use the Windows interop much, WSL2 should be a performance win f…
Yep. With WSL I can seamlessly access files from both Linux and Windows. I use the Terminal (Windows) and various Unix tools for a lot of stuff (compiling & testing on Posix, objdump, debugging). And I use Windows GUI tools for editing (Sublime), diffing (BeyondCompare), and so on. I get the best of both worlds. But WSL2 file access in `/mnt/c/` is now unbearably slow. So I just stick with WSL1. From what I've read,…
The files would live in WSL 2 directly, but then you access them over Windows through the WSL network path?
I don't have insiders installed so I don't know how slow that would be. Like if you CTRL+p'd in Sublime Text, would it have to grab a list of files from over the network on every call, or does it cache these files locally on a per ST session basis, etc..
There's also maybe the option of running ST natively in WSL 2 and expose its GUI over an X-server. I know latency there is very good (near native) because I've done it in the past. This also gives you the added advantage of ST being able to know about your Linux environment which could be nice for linting and other things that require having your programming runtime installed in the same place as your editor.
You can still have shortcuts too in Windows, for pinning stuff to your taskbar or having right click menus. I do this with Vim now with WSL 1, where I have a custom "open with Vim" right click menu in explorer that opens terminal / native Linux Vim that's installed in WSL.
> 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.
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).
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?
From what I understand, WSL 1 doesn't have proper access to GPU, and for WSL 2 / Hyper-V, GPU pass-through isn't a thing for cards such as the 1080TI.
On Windows, Conda / Anaconda is quite buggy, and dealing with a regular python install through the CMD command line isn't too pleasant either.
Looks like the modern macbooks don't have any CUDA-capable GPUs. What do folks use for their ML projects? AWS?
Earlier quoted context omitted.
> I thought it was a thin translation layer between the kernels? WSL1 was like that, but it was severely handicapped by NT filesystem performance, especially for small files or metadata operations. There are a lot of small operations that are more than 2 orders of magnitude slower on Windows than on Linux, and a lot of Linux software just expects them to be fast, so WSL1 is not a great experience for a lot of stuff.
Personally I never had a problem with filesystem performance on WSL 1. I certainly don't think it was so bad that the whole thing needed to be scrapped in favor of a virtual machine.
Earlier quoted context omitted.
What makes windows better than osx for VR?
Well, one of the biggest platforms for VR gaming has dropped support for Mac OS. https://www.theverge.com/2020/5/1/21244468/steam-mac-support... Coupled with a history of GPU driver support usually being best on Windows and having good GPU support is usually pretty important for VR, its pretty clear why Windows is probably the best platform for VR development at the moment.
https://www.engadget.com/half-life-alyx-adds-1-million-vr-us...
What I haven't seen mentioned is that WSL 1 nor 2 work with the modern Machine Learning GPU acceleration. From what I understand, WSL 1 doesn't have proper access to GPU, and for WSL 2 / Hyper-V, GPU pass-through isn't a thing for cards such as the 1080TI. On Windows, Conda / Anaconda is quite buggy, and dealing with a regular python install through the CMD command line isn't too pleasant either. Looks like the moder…
I'd suggest avoiding MacBooks if you are in the ML field, or having a dedicated desktop machine somewhere that you connect to.