31–40 of 252 posts
Earlier quoted context omitted.
I'm curious what you mean by "properly supports Windows." Are you on a version of Windows that supports WSL2 (Windows Subsystem for Linux)?
WSL is great but it’s basically a convenient VM. It’s no longer windows, as far as I’m concerned.
Earlier quoted context omitted.
What are the features that are done differently, or in other words, why would I choose Nushell over PowerShell?
You don't. The good thing is you have alternative in case you need it. Performance might be different in specific case.
Earlier quoted context omitted.
WSL is great but it’s basically a convenient VM. It’s no longer windows, as far as I’m concerned.
It's literally a subsystem. It's integrated in many ways you would not use to describe a "VM". I don't understand the aversion nor the confusion.
Earlier quoted context omitted.
You don't. The good thing is you have alternative in case you need it. Performance might be different in specific case.
Well, they were replying to a post that said this is powershell done right. Seems very relevant to ask what the done right part is.
"Done right" is probably that it is not done by MS and that it is developed in Rust. That ignores universe of other aspects.
>This is just an example from YAML to JSON, but you can convert much more formats into other formats. >open dev/home-impermanence/tests/impermanence.yml | to json I can do it with PowerShell: $os_list = (Get-Content -Path "C:\temp\operating-systems.yml" | ConvertFrom-Yaml) Set-Content -Path "C:\temp\PowerShell_operating-systems.json" -Value ($os_list | ConvertTo-Json)
>This is just an example from YAML to JSON, but you can convert much more formats into other formats. >open dev/home-impermanence/tests/impermanence.yml | to json I can do it with PowerShell: $os_list = (Get-Content -Path "C:\temp\operating-systems.yml" | ConvertFrom-Yaml) Set-Content -Path "C:\temp\PowerShell_operating-systems.json" -Value ($os_list | ConvertTo-Json)
Earlier quoted context omitted.
It's literally a subsystem. It's integrated in many ways you would not use to describe a "VM". I don't understand the aversion nor the confusion.
I thought since WSL2 it’s just a Hyper-V VM with some nice upfront configuration (like mounting all windows disks)?
And to be clear, WSL2 is very much integrated into windows via the filesystem and networking. I like to think of the networking more akin to docker than anything else.
Should probably be switched to the official project page rather than a subpage on an unrelated party website: https://www.nushell.sh/ It’s a lot better at introducing Nushell and feels like a proper landing page.
Earlier quoted context omitted.
Well, they were replying to a post that said this is powershell done right. Seems very relevant to ask what the done right part is.
Anybody can say anything, that doesnt mean it should be taken seriously. "Done right" is probably that it is not done by MS and that it is developed in Rust. That ignores universe of other aspects.
Earlier quoted context omitted.
Well, it is a good point, since nowadays PowerShell is also cross-platform, and seems to have more features than nushell does. Though the true reason is: I haven't really found the time to. Changing a shell is really stressful since you have to unlearn / relearn lots of things from muscle memory, and PowerShell's huge deviance from the rest of the POSIX-y world doesn't help. At least in nushell `rm -rf` works, the sa…
> PowerShell's huge deviance from the rest of the POSIX-y world doesn't help In PowerShell (on Windows), `rm` is an alias to `Remove-Item`[0]. Therefore, rm -r -fo An extra dash, extra space, and extra letter isn't too bad by my books. Furthermore, in scripts, aliases are discouraged by PSScriptAnalyzer[1]; IDEs (PowerShell ISE, VS Code PowerShell extension) also support code completion, so: Remove-Item -Recurse -For…
rm -r -fo thing1, thing2
Or in the non-recursive way:
rm thing1, thing2, thing3