https://news.ycombinator.com/item?id=27525031 (763 points | 1 year ago | 398 comments)
https://news.ycombinator.com/item?id=20783006 (1477 points | 3 years ago | 366 comments)
11–20 of 252 posts
https://news.ycombinator.com/item?id=27525031 (763 points | 1 year ago | 398 comments)
https://news.ycombinator.com/item?id=20783006 (1477 points | 3 years ago | 366 comments)
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/
> With nushell, it feels like I finally have a better tool to create more reliable, robust, portable and faster command pipelines. The learning curve didn't feel too hard, but maybe it's because I'm already used to functional programming.
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 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.
(Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)
I use it as my primary driver, for the sole reason is that it's the only cross-platform shell that properly supports Windows (without resorting to Cygwin/MSYS, which has performance issues and many pain points). I'm still getting used to the syntax though... (Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)
I use it as my primary driver, for the sole reason is that it's the only cross-platform shell that properly supports Windows (without resorting to Cygwin/MSYS, which has performance issues and many pain points). I'm still getting used to the syntax though... (Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)
I use it as my primary driver, for the sole reason is that it's the only cross-platform shell that properly supports Windows (without resorting to Cygwin/MSYS, which has performance issues and many pain points). I'm still getting used to the syntax though... (Edit: forgot to mention Powershell, since nowadays it also works on Macs and Linux)
I'm curious what you mean by "properly supports Windows." Are you on a version of Windows that supports WSL2 (Windows Subsystem for Linux)?
Nushell is PowerShell done right.