91–100 of 252 posts
Earlier quoted context omitted.
Is there a reason some shells like fish (and now nushell) are non-POSIX? Some things are different than other things. It's the same reason that not all desserts are pie, and not all automobiles are trucks.
I guess I was more curious about the cost/benefit. Given a well defined standard like POSIX, and the difficulty of swapping in a new shell into Windows, I wasn't seeing why you'd buck the well established trend.
Earlier quoted context omitted.
So HN is not supposed to allow blog posts about projects but must always swap out for the project site itself? As someone who writes blog posts about projects, I hope not! It's not like this blog post is affiliate spam.
If the project site is better written and has the same content, yeah, I would prefer to see it. But this is not the case here.
The project page is better in any respect. I was going to dismiss it and was writing a comment about how the landing page should be improved before realising it was just a blog page. That’s why I’m linking it.
Earlier quoted context omitted.
I thought since WSL2 it’s just a Hyper-V VM with some nice upfront configuration (like mounting all windows disks)?
I'm pretty sure Windows itself, as in your desktop, runs virtualized under many circumstances; and nobody seems to complain about Hyper-V then. 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.
Earlier quoted context omitted.
> anti-semantic Why? > non-portable PowerShell 6 and later run on Windows, macOS, and Linux. > verbose This is by design.
Its not verbose. Its just that people that use it like to share verbose stuff as it is more helpful to others.
When I'm using PowerShell as a scripting environment, I use the full name for every command and parameter, and even include the names of positional parameters.
I love that it can do both.
Earlier quoted context omitted.
When PS has pushd, popd and dirs -v I’ll switch.
It has Push-Location and Pop-Location, which are aliased to pushd and popd. IDK about dirs -v.
Earlier quoted context omitted.
Is there a reason some shells like fish (and now nushell) are non-POSIX? Some things are different than other things. It's the same reason that not all desserts are pie, and not all automobiles are trucks.
I guess I was more curious about the cost/benefit. Given a well defined standard like POSIX, and the difficulty of swapping in a new shell into Windows, I wasn't seeing why you'd buck the well established trend.
I thought the original Nushell was written by Jonathan Turner. Is this different? Some attribution in the article would help. (Thanks for pointing, there are links to original in the article) https://www.nushell.sh/
> I packaged it for OpenBSD, so it's available on -current (and will be in releases after 7.3 is out), the port could be used on 7.2 with no effort. I think this is what makes it sound like the author of the article is the author of nushell. My first reading led me to believe the same, but she is "only" responsible for the OpenBSD package.
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.