21–30 of 78 posts
Omg scoop looks awesome, how have I not heard of it before?
Have you heard about WinGet? It's the official package manager for Windows: https://github.com/microsoft/winget-cli
That's why you trash WSL2 and just stick with WSL1. I'm surprised they didn't mention it at all.
Keep MSYS2 around for where WSL1 doesn't suffice, but that should be fairly infrequent.
Earlier quoted context omitted.
Oh wow, I didn't know about this, thanks for posting! For others, it really is just as easy as `ls | clip.exe` to pipe into your clipboard on WSL. `ls | tee clip.exe` if you want to print as well as copy. And of course you can just set an alias if you want to shorten clip.exe to clip. Great tip! Thank you!
It's implimented as a magic filename? Not a virtual or real file that actually appears in a filesystem? You don't have to do something like mount a virtual fs that maps to your host windows fs like a bind mount or nfs mount, and also add that fs to PATH? If so, that sounds terrible, and very Microsoft.
Mutt is exactly something that would be nice to rewrite in Rust, moreover, splitting into various crates of working with email, so that it will be possible to reuse the same code for both TUI and GUI clients.
Why must a generaly good improvement these days always start on HN with "rewrite in rust" like it's the only language which still matters. Leave that up to the developer to what they prefer for the job.
Earlier quoted context omitted.
It's implimented as a magic filename? Not a virtual or real file that actually appears in a filesystem? You don't have to do something like mount a virtual fs that maps to your host windows fs like a bind mount or nfs mount, and also add that fs to PATH? If so, that sounds terrible, and very Microsoft.
The entire point of WSL is seamless integration. Windows drives are automatically mounted as /mnt/c, the Windows PATH is added to the Linux one, and it can run Windows .exe files and communicate with their standard I/O.
So good then.
Mutt is exactly something that would be nice to rewrite in Rust, moreover, splitting into various crates of working with email, so that it will be possible to reuse the same code for both TUI and GUI clients.
> so that it will be possible to reuse the same code for both TUI and GUI clients. Why must a generaly good improvement these days always start on HN with "rewrite in rust" like it's the only language which still matters. Leave that up to the developer to what they prefer for the job.
Omg scoop looks awesome, how have I not heard of it before?
The genius insight behind Scoop is that Windows doesn't need a dependency manager because pretty much all programs ship with their dependencies included. So all you need is a way to download & run installers automatically, from the command line, into a Scoop-controlled directory.
> WSL is nice, but it takes up a lot of RAM on my system. I prefer to use MSYS2. That's why you trash WSL2 and just stick with WSL1. I'm surprised they didn't mention it at all. Keep MSYS2 around for where WSL1 doesn't suffice, but that should be fairly infrequent.
WSL1 was great and I loved it better on many aspect, until you needed to touch the filesystem.
> WSL is nice, but it takes up a lot of RAM on my system. I prefer to use MSYS2. That's why you trash WSL2 and just stick with WSL1. I'm surprised they didn't mention it at all. Keep MSYS2 around for where WSL1 doesn't suffice, but that should be fairly infrequent.
WSL2 is also pretty good at giving RAM back to the host Windows. I guess you're really running thin on resources if this doesn't do enough.